20210528 - a Slackware upgrade causes the page rendering to fail. Apologies and I am looking for the cause.
Reported as https://forum.dokuwiki.org/d/19270-dokuwiki-instance-no-longer-rendering-some-syntax-correctly

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
slackbook:process_control [2012/09/08 19:44 (UTC)]
mfillpot [top] updated section to match original text and formatting
slackbook:process_control [2012/10/14 15:53 (UTC)]
mfillpot removed all bash flags
Line 71: Line 71:
 <note> <note>
 This is distinct from the //-aux// argument, but in most cases This is distinct from the //-aux// argument, but in most cases
-the two arguments are equivilant. This is a decades-old relic. For more+the two arguments are equivalent. This is a decades-old relic. For more
 information, see the man page for //**ps**//. information, see the man page for //**ps**//.
 </note> </note>
Line 321: Line 321:
 ===== cron ===== ===== cron =====
  
-Ok, so we've learned many different ways of viewing the active processes on our system and means of signalling them, but what if we want to run a process periodically? Fortunately, Slackware includes just the thing, crond(8). cron runs processes for every user on the schedule that user demands. This makes it very useful for processes that need to be run periodically, but don't require full daemonization, such as backup scripts. Every user gets their own entry in the cron database, so non-root users can periodically run processes too. 
  
-In order to run programs from cron, you'll need to use the crontab(1). The man page lists a variety of ways to do this, but the most common method is to pass the [-e] argument. This will lock the user's entry in the cron database (to prevent it from being overwritten by another program), then open that entry with whatever text editor is specified by the VISUAL environment variable. On Slackware systems, this is typically the vi editor. You may need to refer to the chapter on vi before continuing. 
  
-The cron database entries may seem a little archaic at first, but they are highly flexible. Each uncommented line is processed by crond and the command specified is run if all the time conditions match.+Ok, so we've learned many different ways of viewing the active 
 +processes on our system and means of signalling them, but what if we 
 +want to run a process periodically? Fortunately, Slackware includes 
 +just the thing, **//crond//**(8). cron runs 
 +processes for every user on the schedule that user demands. This makes 
 +it very useful for processes that need to be run periodically, but 
 +don't require full daemonization, such as backup scripts. Every user 
 +gets their own entry in the cron database, so non-root users can 
 +periodically run processes too. 
 + 
 + 
 +In order to run programs from cron, you'll need to use the 
 +**//crontab//**(1). The man page lists a variety of 
 +ways to do this, but the most common method is to pass the 
 +//-e// argument. This will lock the user's entry in the cron 
 +database (to prevent it from being overwritten by another program), 
 +then open that entry with whatever text editor is specified by the 
 +VISUAL environment variable. On Slackware systems, this is typically 
 +the **//vi//** editor. You may need to refer to the 
 +chapter on **//vi//** before continuing. 
 + 
 + 
 +The cron database entries may seem a little archaic at first, but they 
 +are highly flexible. Each uncommented line is processed by 
 +**//crond//** and the command specified is run if 
 +all the time conditions match. 
  
 <code> <code>
Line 333: Line 357:
 </code> </code>
  
-As mentioned before, the syntax for cron entries is a little difficult to understand at first, so let's look at each part individually. From left to right, the different sections are: Minute, Hour, Day, Month, Week Day, and Command. Any asterisk ***** entry matches every minute, hour, day, and so on. So from the example above, the command is //"/usr/local/bin/rsync-slackware64.sh 1>/dev/null 2>&1"//, and it runs every weekday or every week of every month at 2:30 a.m. 
  
-crond will also e-mail the local user with any output the command generates. For this reason, many tasks have their output redirected to ///dev/null//, a special device file that immediately discards everything it receives. In order to make it easier for you to remember these rules, you might wish to paste the following commented text at the top of your own cron entries.+As mentioned before, the syntax for cron entries is a little difficult 
 +to understand at first, so let's look at each part individually. From 
 +left to right, the different sections are: Minute, Hour, Day, Month, 
 +Week Day, and Command. Any asterisk <key>'*'</key> entry matches 
 +every minute, hour, day, and so on. So from the example above, the 
 +command is //"/usr/local/bin/rsync-slackware64.sh 1>/dev/null 2>&1"//, and 
 +it runs every weekday or every week of every month at 2:30 a.m. 
 + 
 + 
 +**//crond//** will also e-mail the local user with 
 +any output the command generates. For this reason, many tasks have 
 +their output redirected to ''/dev/null'', a special 
 +device file that immediately discards everything it receives. In order 
 +to make it easier for you to remember these rules, you might wish to 
 +paste the following commented text at the top of your own cron entries. 
  
 <code> <code>
 +
 # Redirect everything to /dev/null with: # Redirect everything to /dev/null with:
 #   1>/dev/null 2>&1 #   1>/dev/null 2>&1
Line 344: Line 383:
 </code> </code>
  
-By default, Slackware includes a number of entries and comments in root's crontab. These entries make it easier to setup periodic system tasks by creating a number of directories in /etc corresponding to how often the tasks should run. Any script placed within these directories will be run hourly, daily, weekly, or monthly. The names should be self-explanatory: ///etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly,// and ///etc/cron.monthly//.+ 
 +By default, Slackware includes a number of entries and comments in 
 +root's crontab. These entries make it easier to setup periodic system 
 +tasks by creating a number of directories in ''/etc'' 
 +corresponding to how often the tasks should run. Any script placed 
 +within these directories will be run hourly, daily, weekly, or monthly. 
 +The names should be self-explanatory: 
 +''/etc/cron.hourly'', 
 +''/etc/cron.daily'', 
 +''/etc/cron.weekly'', and 
 +''/etc/cron.monthly''. 
 + 
 +====== Chapter Navigation ====== 
 + 
 +**Previous Chapter: [[slackbook:bash|The Bourne Again Shell]]** 
 + 
 +**Next Chapter: [[slackbook:xwindow_system|The X Window System]]** 
 ====== Sources ====== ====== Sources ======
 <!-- If you copy information from another source, then specify that source --> <!-- If you copy information from another source, then specify that source -->
- * Original source: [[http://www.slackbook.org/beta]] + * Original source: [[http://www.slackbook.org/beta]] \\
 <!-- Authors are allowed to give credit to themselves! --> <!-- Authors are allowed to give credit to themselves! -->
-<!-- * Originally written by [[wiki:user:xxx | User X]] -->+ * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson
 <!-- * Contrbutions by [[wiki:user:yyy | User Y]] --> <!-- * Contrbutions by [[wiki:user:yyy | User Y]] -->
  

In Other Languages
QR Code
QR Code slackbook:process_control (generated for current page)