From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FAL4z-0006RX-6c for garchives@archives.gentoo.org; Sat, 18 Feb 2006 05:56:26 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1I5uHbk021774; Sat, 18 Feb 2006 05:56:17 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1I5uGIU030886 for ; Sat, 18 Feb 2006 05:56:16 GMT Message-Id: <200602180556.k1I5uGIU030886@robin.gentoo.org> Received: from lark.gentoo.osuosl.org ([140.211.166.177] helo=lark) by smtp.gentoo.org with smtp (Exim 4.54) id 1FAL4p-0002OA-TQ for gentoo-doc-cvs@lists.gentoo.org; Sat, 18 Feb 2006 05:56:16 +0000 Received: by lark (sSMTP sendmail emulation); Sat, 18 Feb 2006 05:56:15 +0000 From: "Shyam Mani" Date: Sat, 18 Feb 2006 05:56:15 +0000 To: gentoo-doc-cvs@lists.gentoo.org Subject: [gentoo-doc-cvs] cvs commit: cron-guide.xml Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-doc-cvs@gentoo.org Reply-to: docs-team@lists.gentoo.org X-Archives-Salt: f70ec5b7-e8c9-4237-9c9d-88c55532052f X-Archives-Hash: 177e7cf179f006ccb513f71b23885825 fox2mike 06/02/18 05:56:15 Modified: xml/htdocs/doc/en cron-guide.xml Log: You're supposed to leave 1 space after every full stop, NOT 2. **No Content Change** Revision Changes Path 1.12 +43 -43 xml/htdocs/doc/en/cron-guide.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/cron-guide.xml?rev=1.12&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/cron-guide.xml?rev=1.12&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/cron-guide.xml.diff?r1=1.11&r2=1.12&cvsroot=gentoo Index: cron-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- cron-guide.xml 14 Jan 2006 17:04:52 -0000 1.11 +++ cron-guide.xml 18 Feb 2006 05:56:15 -0000 1.12 @@ -1,5 +1,5 @@ - + @@ -31,7 +31,7 @@

Cron is a daemon that runs scheduled tasks based on input from the command -crontab. It accomplishes this task by waking up every minute and +crontab. It accomplishes this task by waking up every minute and checking to see if there are any cron-jobs to run in any of the user crontabs.

@@ -48,8 +48,8 @@

There are at least three cron implementations for you to choose from in -Portage. All of them offer a similar interface, namely the use of -crontab or a similar command. There is also a related utility called +Portage. All of them offer a similar interface, namely the use of +crontab or a similar command. There is also a related utility called Anacron which is meant to work with cron on systems that are not continuously running.

@@ -63,7 +63,7 @@

Before we get started working with cron, you will have to choose which -implementation you want to use. For your convenience, I have collected +implementation you want to use. For your convenience, I have collected information about each one below.

@@ -78,10 +78,10 @@

-Vixie cron is a full featured cron implementation based on SysV cron. Each user +Vixie cron is a full featured cron implementation based on SysV cron. Each user has his own crontab and is allowed to specify environment variables within -that crontab. Unlike the other cron variants, it also offers support for -SELinux and PAM. It supports fewer architectures than Dcron, but more than +that crontab. Unlike the other cron variants, it also offers support for +SELinux and PAM. It supports fewer architectures than Dcron, but more than Fcron.

@@ -112,7 +112,7 @@

-Dcron aims to be a simple, elegant and secure implementation of cron. It does +Dcron aims to be a simple, elegant and secure implementation of cron. It does not allow the specification of environment variables in crontabs and all cron-jobs are run from /bin/sh. Like Vixie cron, each user has his own crontab. @@ -139,7 +139,7 @@

-Fcron aims at replacing Vixie cron and Anacron. It is designed to work on +Fcron aims at replacing Vixie cron and Anacron. It is designed to work on systems that are not continuously running and it is packed with extra features. It has job startup constraints, job serialization controls, the ability to assign nice values to jobs and the ability to schedule jobs to run at system @@ -173,9 +173,9 @@

Anacron is not a cron daemon, it is something that usually works in -conjunction with one. It executes commands at intervals specified in days and +conjunction with one. It executes commands at intervals specified in days and it does not assume that the system is running continuously; it will run jobs -that were missed while the system was down. Anacron usually relies on a cron +that were missed while the system was down. Anacron usually relies on a cron daemon to run it each day.

@@ -219,9 +219,9 @@

The post install messages from some of these cron packages tell you to run crontab /etc/crontab. The /etc/crontab file is your -system crontab. A cron installation can use it in conjunction with +system crontab. A cron installation can use it in conjunction with sys-process/cronbase to run the scripts in -/etc/cron.{daily,hourly,weekly,monthly}. Note that only +/etc/cron.{daily,hourly,weekly,monthly}. Note that only Vixie-cron schedules jobs in /etc/crontab automatically. Dcron and Fcron users will need to run crontab /etc/crontab every time they make changes to /etc/crontab. @@ -234,7 +234,7 @@

Of course, you can choose not to use any system crontab at all. If you chose -Dcron or Fcron, do not run crontab /etc/crontab. If you chose +Dcron or Fcron, do not run crontab /etc/crontab. If you chose vixie-cron, you should comment all lines in /etc/crontab.

@@ -262,7 +262,7 @@

No matter which cron package you use, if you want to allow a user to use -crontab, he will first have to be in the cron group. As an example, if you +crontab, he will first have to be in the cron group. As an example, if you wanted to add the user wepy to the cron group you would run:

@@ -272,14 +272,14 @@

If you're using Dcron, that's all you have to do to give a user access to -crontab. Dcron users may proceed to the next section +crontab. Dcron users may proceed to the next section scheduling cron-jobs, all others will want to keep reading.

If you're using Fcron, you'll want to edit -/etc/fcron/fcron.deny and /etc/fcron/fcron.allow. The +/etc/fcron/fcron.deny and /etc/fcron/fcron.allow. The most secure way is to first deny everyone in /etc/fcron/fcron.deny, and then explicitly allow users in /etc/fcron/fcron.allow.

@@ -298,7 +298,7 @@

Now, say we have a user wepy who should be able to schedule his own -cron-jobs. We would add him to /etc/fcron/fcron.allow as follows: +cron-jobs. We would add him to /etc/fcron/fcron.allow as follows:

@@ -337,7 +337,7 @@
 
 The process of editing crontabs is different for each package, but they all
 support the same basic set of commands: adding and replacing crontabs, editing
-crontabs, deleting crontabs, and listing cron-jobs in crontabs.  The following
+crontabs, deleting crontabs, and listing cron-jobs in crontabs. The following
 list shows you how to run those commands for each package.
 
 
@@ -383,12 +383,12 @@
 
 
 Before we can use any of these commands though, you first need to understand
-the crontab itself.  Each line in a crontab needs to specify five time fields
+the crontab itself. Each line in a crontab needs to specify five time fields
 in the following order: the minutes (0-59), hours (0-23), days of the month
 (1-31), months (1-12), and days of the week (0-7, Monday is 1, Sunday is 0 and
-7).  The days of the weeks and months can be specified by three-letter
-abbreviations like mon, tue, jan, feb, etc.  Each field can also specify a
-range of values (e.g.  1-5 or mon-fri), a comma separated list of values (e.g.
+7). The days of the weeks and months can be specified by three-letter
+abbreviations like mon, tue, jan, feb, etc. Each field can also specify a
+range of values (e.g. 1-5 or mon-fri), a comma separated list of values (e.g.
 1,2,3 or mon,tue,wed) or a range of values with a step (e.g. 1-6/2 as
 1,3,5).
 
@@ -414,13 +414,13 @@
 
 
 Notice how you have to specify specific days of the week and days of the month
-before they are combined.  If you have * for only one of them, the other takes
+before they are combined. If you have * for only one of them, the other takes
 precedence, while * for both just means every day.
 
 
 
 To test what we have just learned, let's go through the steps of actually
-inputting a few cron-jobs.  First, create a file called crons.cron
+inputting a few cron-jobs. First, create a file called crons.cron
 and make it look like the this:
 
 
@@ -462,19 +462,19 @@
 
 
 This crontab should echo "i really like cron" every minute of every hour of
-every day every other month.  Obviously you would only do that if you really
-liked cron.  The crontab will also echo "i like cron a little" at 16:30 every
-day in January and February.  It will also echo "i don't really like cron" at
+every day every other month. Obviously you would only do that if you really
+liked cron. The crontab will also echo "i like cron a little" at 16:30 every
+day in January and February. It will also echo "i don't really like cron" at
 3:10 on the January 1st.
 
 
 
-If you are using Anacron, you should keep reading this section.  Otherwise,
+If you are using Anacron, you should keep reading this section. Otherwise,
 proceed to the next section on editing crontabs.
 
 
 
-Anacron users will want to edit /etc/anacrontab.  This file has
+Anacron users will want to edit /etc/anacrontab. This file has
 four fields: the number of days between each run, the delay in minutes after
 which it runs, the name of the job, and the command to run.
 
@@ -490,7 +490,7 @@
 
 
 Anacron exits after all of the jobs in anacrontab are done, so if we want it to
-check these jobs every day, we will need to use cron.  The instructions at the
+check these jobs every day, we will need to use cron. The instructions at the
 end of the next section tell you how to do that.
 
 
@@ -502,8 +502,8 @@
 
 
 Let's be realistic though, you don't want your system telling you how much you
-like cron every minute.  As a step forward, let's remove that crontab using the
-corresponding remove command from the table above.  We will also list
+like cron every minute. As a step forward, let's remove that crontab using the
+corresponding remove command from the table above. We will also list
 the cron-jobs after, just to make sure it worked.
 
 
@@ -513,15 +513,15 @@

-You should see no cron-jobs in the output from crontab -l. If you do see +You should see no cron-jobs in the output from crontab -l. If you do see jobs listed, that means we failed to remove the crontab, and that you should make sure that you used the correct remove command for your cron package.

Now that we have a clean slate, let's put something useful into the root -crontab. Most people will want to run updatedb on a weekly basis to -make sure that slocate works properly. To add that to your crontab, +crontab. Most people will want to run updatedb on a weekly basis to +make sure that slocate works properly. To add that to your crontab, let's first edit crons.cron again so that it looks like the following:

@@ -543,9 +543,9 @@

Now let's say that you also want to add emerge --sync to your daily -schedule. You could do this by first editing crons.cron and then +schedule. You could do this by first editing crons.cron and then using crontab crons.cron just as we did before, or you could use the -proper edit command from the table above. This gives you a way to edit +proper edit command from the table above. This gives you a way to edit your user's crontab in situ, without depending on external files like crons.cron.

@@ -555,7 +555,7 @@

-That should open your user's crontab with an editor. We want to have emerge +That should open your user's crontab with an editor. We want to have emerge --sync run every day at 6:30 A.M., so we'll make it look something like this:

@@ -569,7 +569,7 @@

Again, check the cron-jobs list as we did in the previous examples to make sure -the jobs are scheduled. If they are all there, then you're all set. +the jobs are scheduled. If they are all there, then you're all set.

@@ -583,7 +583,7 @@

As mentioned earlier, all three of the available cron packages depend on -sys-process/cronbase. The cronbase package creates +sys-process/cronbase. The cronbase package creates /etc/cron.{hourly,daily,weekly,monthly}, and a script called run-crons. You might have noticed that the default /etc/crontab contains something like this: @@ -667,7 +667,7 @@

Remember, each cron package is different and the range of features varies -greatly. Be sure to consult the man pages for crontab, fcrontab or anacrontab, +greatly. Be sure to consult the man pages for crontab, fcrontab or anacrontab, depending on what you use.

-- gentoo-doc-cvs@gentoo.org mailing list