[gentoo-doc-cvs] cvs commit: cron-guide.xml

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Xavier Neys]

neysx       05/07/24 23:00:30

  Modified:    xml/htdocs/doc/en cron-guide.xml
  Log:
  #100161 Added a missing <i>. Also removed unneeded &nbsp;

Revision  Changes    Path
1.5       +9 -9      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.5&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.5&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.4&r2=1.5&cvsroot=gentoo

Index: cron-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- cron-guide.xml	18 Mar 2005 09:48:15 -0000	1.4
+++ cron-guide.xml	24 Jul 2005 23:00:30 -0000	1.5
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.4 2005/03/18 09:48:15 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.5 2005/07/24 23:00:30 neysx Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/cron-guide.xml">
@@ -17,11 +17,11 @@
 </abstract>
 
 <!-- The content of this document is licensed under the CC-BY-SA license -->
-<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
+<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.3</version>
-<date>2005-03-18</date>
+<version>1.4</version>
+<date>2005-07-25</date>
 
 <chapter>
 <title>Cron basics</title>
@@ -262,7 +262,7 @@
 </p>
 
 <pre caption="Adding a user to the cron group">
-gpasswd -a wepy cron
+# <i>gpasswd -a wepy cron</i>
 </pre>
 
 <p>
@@ -339,10 +339,10 @@
 <table>
 <tr>
   <th>Version</th>
-  <th>Edit command&nbsp;</th>
-  <th>Remove command&nbsp;</th>
-  <th>New command&nbsp;</th>
-  <th>List command&nbsp;</th>
+  <th>Edit command</th>
+  <th>Remove command</th>
+  <th>New command</th>
+  <th>List command</th>
 </tr>
 <tr>
   <ti>dcron</ti>



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Xavier Neys]

neysx       06/01/04 11:22:18

  Modified:    xml/htdocs/doc/en cron-guide.xml
  Log:
  #117683 explain cronbase

Revision  Changes    Path
1.7       +99 -39    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.7&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.7&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.6&r2=1.7&cvsroot=gentoo

Index: cron-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- cron-guide.xml	1 Jan 2006 11:51:43 -0000	1.6
+++ cron-guide.xml	4 Jan 2006 11:22:18 -0000	1.7
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.6 2006/01/01 11:51:43 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.7 2006/01/04 11:22:18 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.4</version>
-<date>2005-07-25</date>
+<version>1.5</version>
+<date>2005-01-04</date>
 
 <chapter>
 <title>Cron basics</title>
@@ -51,7 +51,14 @@
 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 
-running.  
+running.
+</p>
+
+<p>
+It is also worth noting that all three of the available cron packages depend on
+<c>sys-process/cronbase</c>. This package is not technically depended on by any
+of the cron packages, but it does provide cron-like functionality that most
+users can appreciate.
 </p>
 
 <p>
@@ -115,13 +122,13 @@
 </p>
 
 <ul>
-<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
-</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
+  </li>
 </ul>
 
 </body>
@@ -144,29 +151,25 @@
 </p>
 
 <ul>
-<li>
-  Designed to work on systems that are not continuously running, i.e. it can run
-  a job after restarting if it was missed
-</li>
-<li>
-  Setting of environment variables and many other options in crontabs 
-</li>
-<li>
-  Each user can have his own crontab, access is controlled by cron.allow and
-  cron.deny
-</li>
-<li>
-  Enhanced crontab syntax with support for many new features
-</li>
+  <li>
+    Designed to work on systems that are not continuously running, i.e. it can
+    run a job after restarting if it was missed
+  </li>
+  <li>Setting of environment variables and many other options in crontabs</li>
+  <li>
+    Each user can have his own crontab, access is controlled by cron.allow and
+    cron.deny
+  </li>
+  <li>Enhanced crontab syntax with support for many new features</li>
 </ul>
 
-
 </body>
 </section>
 
 <section>
 <title>Anacron</title>
 <body>
+
 <p>
 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
@@ -174,8 +177,8 @@
 that were missed while the system was down.  Anacron usually relies on a cron
 daemon to run it each day.
 </p>
-</body>
 
+</body>
 </section>
 </chapter>
 
@@ -208,22 +211,23 @@
 
 </body>
 </section>
-<section>
+<section id="systemtab">
 <title>System crontab</title>
 <body>
 
 <p>
 The post install messages from some of these cron packages tell you to run
 <c>crontab /etc/crontab</c>. The <path>/etc/crontab</path> file is your
-<e>system crontab</e>.  A default Gentoo installation uses it to run the
-scripts in <path>/etc/cron.{daily,hourly,weekly,monthly}</path>.  Note that
+<e>system crontab</e>.  A cron installation can use it in conjunction with
+<c>sys-process/cronbase</c> to run the scripts in
+<path>/etc/cron.{daily,hourly,weekly,monthly}</path>.  Note that only
 Vixie-cron schedules jobs in <path>/etc/crontab</path> automatically. Dcron and
 Fcron users will need to run <c>crontab /etc/crontab</c> every time they make
 changes to <path>/etc/crontab</path>.
 </p>
 
 <p>
-Please note that jobs scheduled in the system crontab will not show up in the
+Please note that jobs scheduled in the system crontab might not show up in the
 list of cron-jobs displayed by <c>crontab -l</c>.
 </p>
 
@@ -339,36 +343,41 @@
 <table>
 <tr>
   <th>Version</th>
-  <th>Edit command</th>
-  <th>Remove command</th>
-  <th>New command</th>
-  <th>List command</th>
+  <th>Edit crontab</th>
+  <th>Remove crontab</th>
+  <th>New crontab</th>
+  <th>List cron-jobs</th>
 </tr>
 <tr>
   <ti>dcron</ti>
   <ti><c>crontab -e</c></ti>
-  <ti><c>crontab -d</c></ti>
+  <ti><c>crontab -d <e>[user]</e></c></ti>
   <ti><c>crontab <e>file</e></c></ti>
   <ti><c>crontab -l</c></ti>
 </tr>
 <tr>
   <ti>fcron</ti>
   <ti><c>fcrontab -e</c></ti>
-  <ti><c>fcrontab -r</c></ti>
+  <ti><c>fcrontab -r <e>[user]</e></c></ti>
   <ti><c>fcrontab <e>file</e></c></ti>
   <ti><c>fcrontab -l</c></ti>
 </tr>
 <tr>
   <ti>vixie-cron</ti>
   <ti><c>crontab -e</c></ti>
-  <ti><c>crontab -r</c></ti>
+  <ti><c>crontab -r <e>[user]</e></c></ti>
   <ti><c>crontab <e>file</e></c></ti>
   <ti><c>crontab -l</c></ti>
 </tr>
 </table>
 
 <note>
-Fcron also makes a symlink to <c>crontab</c>.
+When using the remove command, if no argument is supplied, it deletes the
+current user's crontab.
+</note>
+
+<note>
+Fcron also has a symlink from <c>crontab</c> to <c>fcrontab</c>.
 </note>
 
 <p>
@@ -567,6 +576,57 @@
 </chapter>
 
 <chapter>
+<title>Using cronbase</title>
+<section>
+<body>
+
+<p>
+As mentioned earlier, all three of the available cron packages depend on
+<c>sys-process/cronbase</c>.  The cronbase package creates
+<path>/etc/cron.{hourly,daily,weekly,monthly}</path>, and a script called
+<c>run-crons</c>. You might have noticed that the default
+<path>/etc/crontab</path> contains something like this:
+</p>
+
+<pre caption="Default system crontab">
+*/15 * * * *     test -x /usr/sbin/run-crons &amp;&amp; /usr/sbin/run-crons
+0  *  * * *      rm -f /var/spool/cron/lastrun/cron.hourly
+0  3  * * *      rm -f /var/spool/cron/lastrun/cron.daily
+15 4  * * 6      rm -f /var/spool/cron/lastrun/cron.weekly
+30 5  1 * *      rm -f /var/spool/cron/lastrun/cron.monthly
+</pre>
+
+<p>
+To avoid going into much detail, we can just assume that these commands will
+effectively run your hourly, daily, weekly and monthly scripts. This method of
+scheduling cron-jobs has some important advantages:
+</p>
+
+<ul>
+  <li>
+    They will run even if your computer was off when they were scheduled to run
+  </li>
+  <li>
+    It is easy for package maintainers to place scripts in those well defined
+    places
+  </li>
+  <li>
+    You know exactly where your cron-jobs and your crontab are stored, making
+    it easy for you to backup and restore this part of your system
+  </li>
+</ul>
+
+<note>
+Again, it is useful to point out that Vixie cron automatically reads
+<path>/etc/crontab</path>, while dcron and fcron do not. Please read the <uri
+link="#systemtab">System crontab</uri> section to read more about this.
+</note>
+
+</body>
+</section>
+</chapter>
+
+<chapter>
 <title>Final Notes</title>
 <section>
 <title>Troubleshooting</title>



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Xavier Neys]

neysx       06/01/04 15:11:33

  Modified:    xml/htdocs/doc/en cron-guide.xml
  Log:
  s/2005/2006/ It had to happen!

Revision  Changes    Path
1.8       +2 -2      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.8&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.8&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.7&r2=1.8&cvsroot=gentoo

Index: cron-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- cron-guide.xml	4 Jan 2006 11:22:18 -0000	1.7
+++ cron-guide.xml	4 Jan 2006 15:11:33 -0000	1.8
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.7 2006/01/04 11:22:18 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.8 2006/01/04 15:11:33 neysx Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/cron-guide.xml">
@@ -21,7 +21,7 @@
 <license/>
 
 <version>1.5</version>
-<date>2005-01-04</date>
+<date>2006-01-04</date>
 
 <chapter>
 <title>Cron basics</title>



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Camille Huot]

cam         06/01/14 02:15:40

  Modified:    xml/htdocs/doc/en cron-guide.xml
  Log:
  Style fix, *no content change*

Revision  Changes    Path
1.9       +13 -11    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.9&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.9&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.8&r2=1.9&cvsroot=gentoo

Index: cron-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- cron-guide.xml	4 Jan 2006 15:11:33 -0000	1.8
+++ cron-guide.xml	14 Jan 2006 02:15:40 -0000	1.9
@@ -1,5 +1,5 @@
-<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.8 2006/01/04 15:11:33 neysx Exp $ -->
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.9 2006/01/14 02:15:40 cam Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/cron-guide.xml">
@@ -80,8 +80,9 @@
 <p>
 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 Fcron.
+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.
 </p>
 
 <p>
@@ -126,8 +127,8 @@
     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
+    Access to <c>crontab</c> is limited to the cron group, i.e. it doesn't rely
+    on any external faculties
   </li>
 </ul>
 
@@ -318,8 +319,8 @@
 </impo>
 
 <p>
-For example, if you wanted to allow access to the user <e>wepy</e>, you would add
-him to <path>/etc/cron.allow</path> as follows:
+For example, if you wanted to allow access to the user <e>wepy</e>, you would
+add him to <path>/etc/cron.allow</path> as follows:
 </p>
 
 <pre caption="Permissions in /etc/cron.allow">
@@ -513,8 +514,8 @@
 
 <p>
 You should see no cron-jobs in the output from <c>crontab -l</c>.  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 <e>remove command</e> for your cron package.
+jobs listed, that means we failed to remove the crontab, and that you should
+make sure that you used the correct <e>remove command</e> for your cron package.
 </p>
 
 <p>
@@ -644,7 +645,8 @@
 </li>
 <li>
   <b>Is cron working?</b><br/>
-  Try: * * * * * /bin/echo "foobar" &gt;&gt; /file_you_own, and make sure it works
+  Try: * * * * * /bin/echo "foobar" &gt;&gt; /file_you_own, and make sure it
+  works
 </li>
 <li>
   <b>Is your command working?</b><br/>



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Camille Huot]

cam         06/01/14 02:16:46

  Modified:    xml/htdocs/doc/en cron-guide.xml
  Log:
  Fixed the vixie cron command to remove a user's crontab

Revision  Changes    Path
1.10      +4 -4      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.10&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.10&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.9&r2=1.10&cvsroot=gentoo

Index: cron-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- cron-guide.xml	14 Jan 2006 02:15:40 -0000	1.9
+++ cron-guide.xml	14 Jan 2006 02:16:46 -0000	1.10
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.9 2006/01/14 02:15:40 cam Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.10 2006/01/14 02:16:46 cam 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.5</version>
-<date>2006-01-04</date>
+<version>1.6</version>
+<date>2006-01-14</date>
 
 <chapter>
 <title>Cron basics</title>
@@ -366,7 +366,7 @@
 <tr>
   <ti>vixie-cron</ti>
   <ti><c>crontab -e</c></ti>
-  <ti><c>crontab -r <e>[user]</e></c></ti>
+  <ti><c>crontab -r <e>-u [user]</e></c></ti>
   <ti><c>crontab <e>file</e></c></ti>
   <ti><c>crontab -l</c></ti>
 </tr>



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Shyam Mani]

fox2mike    06/01/14 17:04:52

  Modified:    xml/htdocs/doc/en cron-guide.xml
  Log:
  Grammer fix, thanks to borges ffor catching that one. *No content change*

Revision  Changes    Path
1.11      +2 -2      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.11&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.11&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.10&r2=1.11&cvsroot=gentoo

Index: cron-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- cron-guide.xml	14 Jan 2006 02:16:46 -0000	1.10
+++ cron-guide.xml	14 Jan 2006 17:04:52 -0000	1.11
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.10 2006/01/14 02:16:46 cam Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.11 2006/01/14 17:04:52 fox2mike Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/cron-guide.xml">
@@ -620,7 +620,7 @@
 <note>
 Again, it is useful to point out that Vixie cron automatically reads
 <path>/etc/crontab</path>, while dcron and fcron do not. Please read the <uri
-link="#systemtab">System crontab</uri> section to read more about this.
+link="#systemtab">System crontab</uri> section to learn more about this.
 </note>
 
 </body>



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Shyam Mani]

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 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.11 2006/01/14 17:04:52 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.12 2006/02/18 05:56:15 fox2mike Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/cron-guide.xml">
@@ -31,7 +31,7 @@
 
 <p>
 Cron is a daemon that runs scheduled tasks based on input from the command
-<c>crontab</c>.  It accomplishes this task by waking up every minute and
+<c>crontab</c>. 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.
 </p>
 
@@ -48,8 +48,8 @@
 
 <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
+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 
 running.
 </p>
@@ -63,7 +63,7 @@
 
 <p>
 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.
 </p>
 
@@ -78,10 +78,10 @@
 <body>
 
 <p>
-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.
 </p>
 
@@ -112,7 +112,7 @@
 <body>
 
 <p>
-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 <path>/bin/sh</path>. Like Vixie cron, each user has his
 own crontab.
@@ -139,7 +139,7 @@
 <body>
 
 <p>
-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 @@
 
 <p>
 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.
 </p>
 
@@ -219,9 +219,9 @@
 <p>
 The post install messages from some of these cron packages tell you to run
 <c>crontab /etc/crontab</c>. The <path>/etc/crontab</path> file is your
-<e>system crontab</e>.  A cron installation can use it in conjunction with
+<e>system crontab</e>. A cron installation can use it in conjunction with
 <c>sys-process/cronbase</c> to run the scripts in
-<path>/etc/cron.{daily,hourly,weekly,monthly}</path>.  Note that only
+<path>/etc/cron.{daily,hourly,weekly,monthly}</path>. Note that only
 Vixie-cron schedules jobs in <path>/etc/crontab</path> automatically. Dcron and
 Fcron users will need to run <c>crontab /etc/crontab</c> every time they make
 changes to <path>/etc/crontab</path>.
@@ -234,7 +234,7 @@
 
 <p>
 Of course, you can choose not to use any system crontab at all. If you chose
-Dcron or Fcron, do <e>not</e> run <c>crontab /etc/crontab</c>.  If you chose
+Dcron or Fcron, do <e>not</e> run <c>crontab /etc/crontab</c>. If you chose
 vixie-cron, you should comment all lines in <path>/etc/crontab</path>.
 </p>
 
@@ -262,7 +262,7 @@
 
 <p>
 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 <e>wepy</e> to the cron group you would run:
 </p>
 
@@ -272,14 +272,14 @@
 
 <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>
 
 <p>
 If you're using <b>Fcron</b>, you'll want to edit
-<path>/etc/fcron/fcron.deny</path> and <path>/etc/fcron/fcron.allow</path>.  The
+<path>/etc/fcron/fcron.deny</path> and <path>/etc/fcron/fcron.allow</path>. The
 most secure way is to first deny everyone in <path>/etc/fcron/fcron.deny</path>,
 and then explicitly allow users in <path>/etc/fcron/fcron.allow</path>.
 </p>
@@ -298,7 +298,7 @@
 
 <p>
 Now, say we have a user <e>wepy</e> who should be able to schedule his own
-cron-jobs.  We would add him to <path>/etc/fcron/fcron.allow</path> as follows:
+cron-jobs. We would add him to <path>/etc/fcron/fcron.allow</path> as follows:
 </p>
 
 <pre caption="Permissions in fcron.allow">
@@ -337,7 +337,7 @@
 <p>
 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.
 </p>
 
@@ -383,12 +383,12 @@
 
 <p>
 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 <e>step</e> (e.g. 1-6/2 as
 1,3,5).
 </p>
@@ -414,13 +414,13 @@
 
 <note>
 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.
 </note>
 
 <p>
 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 <path>crons.cron</path>
+inputting a few cron-jobs. First, create a file called <path>crons.cron</path>
 and make it look like the this:
 </p>
 
@@ -462,19 +462,19 @@
 
 <p>
 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.
 </p>
 
 <p>
-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 <uri link="#editing">editing crontabs</uri>.
 </p>
 
 <p>
-Anacron users will want to edit <path>/etc/anacrontab</path>.  This file has
+Anacron users will want to edit <path>/etc/anacrontab</path>. 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.
 </p>
@@ -490,7 +490,7 @@
 
 <p>
 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.
 </p>
 
@@ -502,8 +502,8 @@
 
 <p>
 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 <e>remove command</e> from the table above.  We will also list
+like cron every minute. As a step forward, let's remove that crontab using the
+corresponding <e>remove command</e> from the table above. We will also list
 the cron-jobs after, just to make sure it worked.
 </p>
 
@@ -513,15 +513,15 @@
 </pre>
 
 <p>
-You should see no cron-jobs in the output from <c>crontab -l</c>.  If you do see
+You should see no cron-jobs in the output from <c>crontab -l</c>. 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 <e>remove command</e> for your cron package.
 </p>
 
 <p>
 Now that we have a clean slate, let's put something useful into the <b>root</b>
-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,
+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: 
 </p>
@@ -543,9 +543,9 @@
 
 <p>
 Now let's say that you also want to add <c>emerge --sync</c> to your daily
-schedule.  You could do this by first editing <path>crons.cron</path> and then
+schedule. You could do this by first editing <path>crons.cron</path> and then
 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
+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>. 
 </p>
@@ -555,7 +555,7 @@
 </pre>
 
 <p>
-That should open your user's crontab with an editor.  We want to have <c>emerge
+That should open your user's crontab with an editor. We want to have <c>emerge
 --sync</c> run every day at 6:30 A.M., so we'll make it look something like
 this:
 </p>
@@ -569,7 +569,7 @@
 
 <p>
 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.
 </p>
 
 </body>
@@ -583,7 +583,7 @@
 
 <p>
 As mentioned earlier, all three of the available cron packages depend on
-<c>sys-process/cronbase</c>.  The cronbase package creates
+<c>sys-process/cronbase</c>. The cronbase package creates
 <path>/etc/cron.{hourly,daily,weekly,monthly}</path>, and a script called
 <c>run-crons</c>. You might have noticed that the default
 <path>/etc/crontab</path> contains something like this:
@@ -667,7 +667,7 @@
 
 <p>
 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.
 </p>
 



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Xavier Neys]

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" &gt;&gt; /file_you_own, and make sure it
+  Try: * * * * * /bin/echo "foobar" &gt;&gt; /file_you_own and make sure it
   works
 </li>
 <li>
   <b>Is your command working?</b><br/>
-  Try: * * * * * /bin/foobar &gt; /file_you_own 2&gt;&amp;1, look for errors
+  Try: * * * * * /bin/foobar &gt; /file_you_own 2&gt;&amp;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>
 



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Jose Luis Rivero]

yoswink     06/06/22 00:42:58

  Modified:             cron-guide.xml
  Log:
  Fixed broken anchor since they are case-sensitive. Very few translations seem to be affected. They have been mailed so we don't need to bump version.

Revision  Changes    Path
1.14                 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.14&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.14&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.13&r2=1.14&cvsroot=gentoo

Index: cron-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- cron-guide.xml	20 Feb 2006 12:33:47 -0000	1.13
+++ cron-guide.xml	22 Jun 2006 00:42:57 -0000	1.14
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.13 2006/02/20 12:33:47 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.14 2006/06/22 00:42:57 yoswink Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/cron-guide.xml">
@@ -336,7 +336,7 @@
 </body>
 </section>
 
-<section id="Scheduling">
+<section id="scheduling">
 <title>Scheduling cron-jobs</title>
 <body>
 



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Joshua Saddler]

nightmorph    08/01/27 00:42:40

  Modified:             cron-guide.xml
  Log:
  added bcron info, bug 197248

Revision  Changes    Path
1.16                 xml/htdocs/doc/en/cron-guide.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?r1=1.15&r2=1.16

Index: cron-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- cron-guide.xml	29 Apr 2007 16:41:28 -0000	1.15
+++ cron-guide.xml	27 Jan 2008 00:42:40 -0000	1.16
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.15 2007/04/29 16:41:28 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.16 2008/01/27 00:42:40 nightmorph Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/cron-guide.xml">
@@ -11,6 +11,9 @@
 <author title="Editor">
   <mail link="neysx@gentoo.org">Xavier Neys</mail>
 </author>
+<author title="Editor">
+  <mail link="nightmorph"/>
+</author>
 
 <abstract>
 This guide describes how to setup and use cron.
@@ -20,8 +23,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.8</version>
-<date>2007-04-29</date>
+<version>1.9</version>
+<date>2008-01-26</date>
 
 <chapter>
 <title>Cron basics</title>
@@ -47,15 +50,14 @@
 <body>
 
 <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
-running.
+There are a few 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 running.
 </p>
 
 <p>
-It is also worth noting that all three of the available cron packages depend on
+It is also worth noting that all of the available cron packages depend on
 <c>sys-process/cronbase</c>. This package is not technically depended on by any
 of the cron packages, but it does provide cron-like functionality that most
 users can appreciate.
@@ -166,7 +168,31 @@
 
 </body>
 </section>
+<section>
+<title>bcron</title>
+<body>
 
+<p>
+bcron is a new cron system designed with secure operations in mind. To do this,
+the system is divided into several separate programs, each responsible for a
+separate task, with strictly controlled communications between them. The user
+interface is a drop-in replacement for similar systems (such as vixie-cron), but
+the internals differ greatly. For more information, see the bcron homepage at
+<uri>http://untroubled.org/bcron/</uri>.
+</p>
+
+<p>
+Features of <c>sys-process/bcron</c>:
+</p>
+
+<ul>
+  <li>Drop-in replacement for vixie-cron</li>
+  <li>Multiprocess design</li>
+  <li>Native daylight savings time support</li>
+</ul>
+
+</body>
+</section>
 <section>
 <title>Anacron</title>
 <body>
@@ -235,7 +261,7 @@
 <p>
 Of course, you can choose not to use any system crontab at all. If you chose
 Dcron or Fcron, do <e>not</e> run <c>crontab /etc/crontab</c>. If you chose
-vixie-cron, you should comment all lines in <path>/etc/crontab</path>.
+vixie-cron or bcron, you should comment all lines in <path>/etc/crontab</path>.
 </p>
 
 <pre caption="Commenting all lines in /etc/crontab">
@@ -370,7 +396,7 @@
   <ti><c>fcrontab -l</c></ti>
 </tr>
 <tr>
-  <ti>vixie-cron</ti>
+  <ti>vixie-cron &amp; bcron</ti>
   <ti><c>crontab -e</c></ti>
   <ti><c>crontab -r <e>-u [user]</e></c></ti>
   <ti><c>crontab <e>file</e></c></ti>
@@ -588,7 +614,7 @@
 <body>
 
 <p>
-As mentioned earlier, all three of the available cron packages depend on
+As mentioned earlier, all of the available cron packages depend on
 <c>sys-process/cronbase</c>. The cronbase package creates
 <path>/etc/cron.{hourly,daily,weekly,monthly}</path>, and a script called
 <c>run-crons</c>. You might have noticed that the default
@@ -624,7 +650,7 @@
 </ul>
 
 <note>
-Again, it is useful to point out that Vixie cron automatically reads
+Again, it is useful to point out that Vixie cron and bcron automatically read
 <path>/etc/crontab</path>, while dcron and fcron do not. Please read the <uri
 link="#systemtab">System crontab</uri> section to learn more about this.
 </note>



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

[gentoo-doc-cvs] cvs commit: cron-guide.xml

[Joshua Saddler]

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" &gt;&gt; /file_you_own and make sure it
-  works
-</li>
-<li>
-  <b>Is your command working?</b><br/>
-  Try: * * * * * /bin/foobar &gt; /file_you_own 2&gt;&amp;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" &gt;&gt;
+    /file_you_own and make sure it works
+  </li>
+  <li>
+    <b>Is your command working?</b> Try: * * * * * /bin/foobar &gt;
+    /file_you_own 2&gt;&amp;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>



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