neysx 06/02/20 12:33:47 Modified: xml/htdocs/doc/en cron-guide.xml Log: #123224 minor touch-ups
Revision Changes Path 1.13 +34 -28 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.13&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.13&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.12&r2=1.13&cvsroot=gentoo Index: cron-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- cron-guide.xml 18 Feb 2006 05:56:15 -0000 1.12 +++ cron-guide.xml 20 Feb 2006 12:33:47 -0000 1.13 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.12 2006/02/18 05:56:15 fox2mike Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.13 2006/02/20 12:33:47 neysx Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/cron-guide.xml"> @@ -20,8 +20,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>1.6</version> -<date>2006-01-14</date> +<version>1.7</version> +<date>2006-02-20</date> <chapter> <title>Cron basics</title> @@ -46,11 +46,11 @@ <title>The de facto cron</title> <body> -<p> +<p> 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 <c>crontab</c> 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 +Anacron which is meant to work with cron on systems that are not continuously running. </p> @@ -195,8 +195,8 @@ <pre caption="Installing cron"> # <i>emerge dcron</i> -# <i>rc-update add dcron default</i> # <i>/etc/init.d/dcron start</i> +# <i>rc-update add dcron default</i> </pre> <p> @@ -206,8 +206,8 @@ <pre caption="Installing anacron"> # <i>emerge anacron</i> -# <i>rc-update add anacron default</i> # <i>/etc/init.d/anacron start</i> +# <i>rc-update add anacron default</i> </pre> </body> @@ -257,7 +257,8 @@ <note> Giving another user access to crontab does not let him run cron-jobs as root. If you want a user to be able to edit the root crontab, you should look into -<c>sudo</c>. +<c>sudo</c>. Please read our <uri link="/doc/en/sudo-guide.xml">Gentoo +Sudo(ers) Guide</uri> for more details. </note> <p> @@ -270,9 +271,14 @@ # <i>gpasswd -a wepy cron</i> </pre> +<note> +When adding a user to the cron group, make sure that the user log out and back +in for the group change to take effect. +</note> + <p> If you're using <b>Dcron</b>, 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 <uri link="#scheduling">scheduling cron-jobs</uri>, all others will want to keep reading. </p> @@ -288,7 +294,7 @@ <b>If neither <path>/etc/fcron/fcron.allow</path> nor <path>/etc/fcron/fcron.deny</path> exist, all users in the cron group will be allowed to use crontab</b>. -fcron comes with a default <path>fcron.allow</path> which <b>allows all +fcron comes with a default <path>fcron.allow</path> which <b>allows all users</b> in the cron group access to fcrontab. </impo> @@ -307,7 +313,7 @@ <p> If you chose <b>Vixie cron</b>, you'll probably just want to edit -<path>/etc/cron.allow</path>. +<path>/etc/cron.allow</path>. </p> <impo> @@ -400,7 +406,7 @@ <pre caption="Examples"> <comment># Run /bin/false every minute year round</comment> -* * * * * /bin/false +* * * * * /bin/false <comment># Run /bin/false at 1:35 on the mon,tue,wed and the 4th of every month</comment> 35 1 4 * mon-wed /bin/false @@ -427,9 +433,9 @@ <pre caption="Editing crons.cron"> $ <i>nano crons.cron</i> <comment>#Mins Hours Days Months Day of the week</comment> -10 3 1 1 * /bin/echo "i don't really like cron" -30 16 * 1,2 * /bin/echo "i like cron a little" -* * * 1-12/2 * /bin/echo "i really like cron" +10 3 1 1 * /bin/echo "I don't really like cron" +30 16 * 1,2 * /bin/echo "I like cron a little" +* * * 1-12/2 * /bin/echo "I really like cron" </pre> <p> @@ -442,12 +448,12 @@ </pre> <note> -You won't actually see the output from these echo commands unless you use +You won't actually see the output from these echo commands unless you use redirection. </note> <p> -To verify the cron-jobs you scheduled, we'll use the proper <e>list command</e> +To verify the cron-jobs you scheduled, we'll use the proper <e>list command</e> from the table above. </p> @@ -461,10 +467,10 @@ </p> <p> -This crontab should echo "i really like cron" every minute of every hour of +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 +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. </p> @@ -480,12 +486,12 @@ </p> <p> -For example, to have it run <c>echo "i like anacron"</c> every 5 days, 10 +For example, to have it run <c>echo "I like anacron"</c> every 5 days, 10 minutes after Anacron is started, you would have: </p> <pre caption="/etc/anacrontab"> -5 10 wasting-time /bin/echo "i like anacron" +5 10 wasting-time /bin/echo "I like anacron" </pre> <p> @@ -523,7 +529,7 @@ crontab. Most people will want to run <c>updatedb</c> on a weekly basis to make sure that <c>slocate</c> works properly. To add that to your crontab, let's first edit <path>crons.cron</path> again so that it looks like the -following: +following: </p> <pre caption="A real crontab"> @@ -547,7 +553,7 @@ using <c>crontab crons.cron</c> just as we did before, or you could use the proper <e>edit command</e> from the table above. This gives you a way to edit your user's crontab in situ, without depending on external files like -<path>crons.cron</path>. +<path>crons.cron</path>. </p> <pre caption="Editing a crontab in place"> @@ -641,16 +647,16 @@ <ul> <li> <b>Is cron running?</b><br/> - Run <c>ps ax | grep cron</c>, make sure it shows up! + Run <c>ps ax | grep cron</c> and make sure it shows up! </li> <li> <b>Is cron working?</b><br/> - Try: * * * * * /bin/echo "foobar" >> /file_you_own, and make sure it + Try: * * * * * /bin/echo "foobar" >> /file_you_own and make sure it works </li> <li> <b>Is your command working?</b><br/> - Try: * * * * * /bin/foobar > /file_you_own 2>&1, look for errors + Try: * * * * * /bin/foobar > /file_you_own 2>&1 and look for errors in /file_you_own </li> <li> @@ -661,7 +667,7 @@ <li> <b>Are there any dead.letter's?</b><br/> cron usually sends mail when there's a problem, check your mail and also - look for ~/dead.letter + look for <path>~/dead.letter</path>. </li> </ul> -- [email protected] mailing list
