nightmorph 08/01/27 00:50:54 Modified: cron-guide.xml Log: fix crappy formatting to bring it up to proper GuideXML standards; no content change
Revision Changes Path 1.17 xml/htdocs/doc/en/cron-guide.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?rev=1.17&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?rev=1.17&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?r1=1.16&r2=1.17 Index: cron-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- cron-guide.xml 27 Jan 2008 00:42:40 -0000 1.16 +++ cron-guide.xml 27 Jan 2008 00:50:54 -0000 1.17 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.16 2008/01/27 00:42:40 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.17 2008/01/27 00:50:54 nightmorph Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/cron-guide.xml"> @@ -92,19 +92,15 @@ </p> <ul> -<li> - Support for SELinux -</li> -<li> - Support for PAM <path>/etc/security/limits.conf</path> -</li> -<li> - Setting of environment variables in crontabs (PATH, SHELL, HOME, etc.) -</li> -<li> - Each user can have his own crontab, access is controlled by cron.allow and - cron.deny -</li> + <li>Support for SELinux</li> + <li>Support for PAM <path>/etc/security/limits.conf</path></li> + <li> + Setting of environment variables in crontabs (PATH, SHELL, HOME, etc.) + </li> + <li> + Each user can have his own crontab; access is controlled by + <path>cron.allow</path> and <path>cron.deny</path> + </li> </ul> </body> @@ -125,9 +121,7 @@ </p> <ul> - <li> - Fast, simple and free of unnecessary features - </li> + <li>Fast, simple and free of unnecessary features</li> <li> Access to <c>crontab</c> is limited to the cron group, i.e. it doesn't rely on any external faculties @@ -361,7 +355,6 @@ </body> </section> - <section id="scheduling"> <title>Scheduling cron-jobs</title> <body> @@ -671,30 +664,27 @@ </p> <ul> -<li> - <b>Is cron running?</b><br/> - 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 - works -</li> -<li> - <b>Is your command working?</b><br/> - Try: * * * * * /bin/foobar > /file_you_own 2>&1 and look for errors - in /file_you_own -</li> -<li> - <b>Can cron run your job?</b><br/> - Check the cron log, usually <path>/var/log/cron.log</path> or - <path>/var/log/messages</path> for errors -</li> -<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 <path>~/dead.letter</path>. -</li> + <li> + <b>Is cron running?</b> Run <c>ps ax | grep cron</c> and make sure it shows + up! + </li> + <li> + <b>Is cron working?</b> Try: * * * * * /bin/echo "foobar" >> + /file_you_own and make sure it works + </li> + <li> + <b>Is your command working?</b> Try: * * * * * /bin/foobar > + /file_you_own 2>&1 and look for errors in /file_you_own + </li> + <li> + <b>Can cron run your job?</b> Check the cron log, usually + <path>/var/log/cron.log</path> or <path>/var/log/messages</path> for errors + </li> + <li> + <b>Are there any <path>dead.letter</path>s?</b> cron usually sends mail when + there's a problem; check your mail and also look for + <path>~/dead.letter</path>. + </li> </ul> <p> @@ -710,5 +700,4 @@ </body> </section> </chapter> - </guide> -- [email protected] mailing list
