| 1 |
nightmorph 08/01/27 00:50:54 |
| 2 |
|
| 3 |
Modified: cron-guide.xml |
| 4 |
Log: |
| 5 |
fix crappy formatting to bring it up to proper GuideXML standards; no content change |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.17 xml/htdocs/doc/en/cron-guide.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?rev=1.17&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?rev=1.17&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?r1=1.16&r2=1.17 |
| 13 |
|
| 14 |
Index: cron-guide.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v |
| 17 |
retrieving revision 1.16 |
| 18 |
retrieving revision 1.17 |
| 19 |
diff -u -r1.16 -r1.17 |
| 20 |
--- cron-guide.xml 27 Jan 2008 00:42:40 -0000 1.16 |
| 21 |
+++ cron-guide.xml 27 Jan 2008 00:50:54 -0000 1.17 |
| 22 |
@@ -1,5 +1,5 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.16 2008/01/27 00:42:40 nightmorph Exp $ --> |
| 25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.17 2008/01/27 00:50:54 nightmorph Exp $ --> |
| 26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 27 |
|
| 28 |
<guide link="/doc/en/cron-guide.xml"> |
| 29 |
@@ -92,19 +92,15 @@ |
| 30 |
</p> |
| 31 |
|
| 32 |
<ul> |
| 33 |
-<li> |
| 34 |
- Support for SELinux |
| 35 |
-</li> |
| 36 |
-<li> |
| 37 |
- Support for PAM <path>/etc/security/limits.conf</path> |
| 38 |
-</li> |
| 39 |
-<li> |
| 40 |
- Setting of environment variables in crontabs (PATH, SHELL, HOME, etc.) |
| 41 |
-</li> |
| 42 |
-<li> |
| 43 |
- Each user can have his own crontab, access is controlled by cron.allow and |
| 44 |
- cron.deny |
| 45 |
-</li> |
| 46 |
+ <li>Support for SELinux</li> |
| 47 |
+ <li>Support for PAM <path>/etc/security/limits.conf</path></li> |
| 48 |
+ <li> |
| 49 |
+ Setting of environment variables in crontabs (PATH, SHELL, HOME, etc.) |
| 50 |
+ </li> |
| 51 |
+ <li> |
| 52 |
+ Each user can have his own crontab; access is controlled by |
| 53 |
+ <path>cron.allow</path> and <path>cron.deny</path> |
| 54 |
+ </li> |
| 55 |
</ul> |
| 56 |
|
| 57 |
</body> |
| 58 |
@@ -125,9 +121,7 @@ |
| 59 |
</p> |
| 60 |
|
| 61 |
<ul> |
| 62 |
- <li> |
| 63 |
- Fast, simple and free of unnecessary features |
| 64 |
- </li> |
| 65 |
+ <li>Fast, simple and free of unnecessary features</li> |
| 66 |
<li> |
| 67 |
Access to <c>crontab</c> is limited to the cron group, i.e. it doesn't rely |
| 68 |
on any external faculties |
| 69 |
@@ -361,7 +355,6 @@ |
| 70 |
|
| 71 |
</body> |
| 72 |
</section> |
| 73 |
- |
| 74 |
<section id="scheduling"> |
| 75 |
<title>Scheduling cron-jobs</title> |
| 76 |
<body> |
| 77 |
@@ -671,30 +664,27 @@ |
| 78 |
</p> |
| 79 |
|
| 80 |
<ul> |
| 81 |
-<li> |
| 82 |
- <b>Is cron running?</b><br/> |
| 83 |
- Run <c>ps ax | grep cron</c> and make sure it shows up! |
| 84 |
-</li> |
| 85 |
-<li> |
| 86 |
- <b>Is cron working?</b><br/> |
| 87 |
- Try: * * * * * /bin/echo "foobar" >> /file_you_own and make sure it |
| 88 |
- works |
| 89 |
-</li> |
| 90 |
-<li> |
| 91 |
- <b>Is your command working?</b><br/> |
| 92 |
- Try: * * * * * /bin/foobar > /file_you_own 2>&1 and look for errors |
| 93 |
- in /file_you_own |
| 94 |
-</li> |
| 95 |
-<li> |
| 96 |
- <b>Can cron run your job?</b><br/> |
| 97 |
- Check the cron log, usually <path>/var/log/cron.log</path> or |
| 98 |
- <path>/var/log/messages</path> for errors |
| 99 |
-</li> |
| 100 |
-<li> |
| 101 |
- <b>Are there any dead.letter's?</b><br/> |
| 102 |
- cron usually sends mail when there's a problem, check your mail and also |
| 103 |
- look for <path>~/dead.letter</path>. |
| 104 |
-</li> |
| 105 |
+ <li> |
| 106 |
+ <b>Is cron running?</b> Run <c>ps ax | grep cron</c> and make sure it shows |
| 107 |
+ up! |
| 108 |
+ </li> |
| 109 |
+ <li> |
| 110 |
+ <b>Is cron working?</b> Try: * * * * * /bin/echo "foobar" >> |
| 111 |
+ /file_you_own and make sure it works |
| 112 |
+ </li> |
| 113 |
+ <li> |
| 114 |
+ <b>Is your command working?</b> Try: * * * * * /bin/foobar > |
| 115 |
+ /file_you_own 2>&1 and look for errors in /file_you_own |
| 116 |
+ </li> |
| 117 |
+ <li> |
| 118 |
+ <b>Can cron run your job?</b> Check the cron log, usually |
| 119 |
+ <path>/var/log/cron.log</path> or <path>/var/log/messages</path> for errors |
| 120 |
+ </li> |
| 121 |
+ <li> |
| 122 |
+ <b>Are there any <path>dead.letter</path>s?</b> cron usually sends mail when |
| 123 |
+ there's a problem; check your mail and also look for |
| 124 |
+ <path>~/dead.letter</path>. |
| 125 |
+ </li> |
| 126 |
</ul> |
| 127 |
|
| 128 |
<p> |
| 129 |
@@ -710,5 +700,4 @@ |
| 130 |
</body> |
| 131 |
</section> |
| 132 |
</chapter> |
| 133 |
- |
| 134 |
</guide> |
| 135 |
|
| 136 |
|
| 137 |
|
| 138 |
-- |
| 139 |
gentoo-doc-cvs@l.g.o mailing list |
Archives