1 |
nightmorph 08/01/27 00:42:40 |
2 |
|
3 |
Modified: cron-guide.xml |
4 |
Log: |
5 |
added bcron info, bug 197248 |
6 |
|
7 |
Revision Changes Path |
8 |
1.16 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.16&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?rev=1.16&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/cron-guide.xml?r1=1.15&r2=1.16 |
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.15 |
18 |
retrieving revision 1.16 |
19 |
diff -u -r1.15 -r1.16 |
20 |
--- cron-guide.xml 29 Apr 2007 16:41:28 -0000 1.15 |
21 |
+++ cron-guide.xml 27 Jan 2008 00:42:40 -0000 1.16 |
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.15 2007/04/29 16:41:28 rane Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.16 2008/01/27 00:42:40 nightmorph Exp $ --> |
26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
27 |
|
28 |
<guide link="/doc/en/cron-guide.xml"> |
29 |
@@ -11,6 +11,9 @@ |
30 |
<author title="Editor"> |
31 |
<mail link="neysx@g.o">Xavier Neys</mail> |
32 |
</author> |
33 |
+<author title="Editor"> |
34 |
+ <mail link="nightmorph"/> |
35 |
+</author> |
36 |
|
37 |
<abstract> |
38 |
This guide describes how to setup and use cron. |
39 |
@@ -20,8 +23,8 @@ |
40 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
41 |
<license/> |
42 |
|
43 |
-<version>1.8</version> |
44 |
-<date>2007-04-29</date> |
45 |
+<version>1.9</version> |
46 |
+<date>2008-01-26</date> |
47 |
|
48 |
<chapter> |
49 |
<title>Cron basics</title> |
50 |
@@ -47,15 +50,14 @@ |
51 |
<body> |
52 |
|
53 |
<p> |
54 |
-There are at least three cron implementations for you to choose from in |
55 |
-Portage. All of them offer a similar interface, namely the use of |
56 |
-<c>crontab</c> or a similar command. There is also a related utility called |
57 |
-Anacron which is meant to work with cron on systems that are not continuously |
58 |
-running. |
59 |
+There are a few cron implementations for you to choose from in Portage. All of |
60 |
+them offer a similar interface, namely the use of <c>crontab</c> or a similar |
61 |
+command. There is also a related utility called Anacron which is meant to work |
62 |
+with cron on systems that are not continuously running. |
63 |
</p> |
64 |
|
65 |
<p> |
66 |
-It is also worth noting that all three of the available cron packages depend on |
67 |
+It is also worth noting that all of the available cron packages depend on |
68 |
<c>sys-process/cronbase</c>. This package is not technically depended on by any |
69 |
of the cron packages, but it does provide cron-like functionality that most |
70 |
users can appreciate. |
71 |
@@ -166,7 +168,31 @@ |
72 |
|
73 |
</body> |
74 |
</section> |
75 |
+<section> |
76 |
+<title>bcron</title> |
77 |
+<body> |
78 |
|
79 |
+<p> |
80 |
+bcron is a new cron system designed with secure operations in mind. To do this, |
81 |
+the system is divided into several separate programs, each responsible for a |
82 |
+separate task, with strictly controlled communications between them. The user |
83 |
+interface is a drop-in replacement for similar systems (such as vixie-cron), but |
84 |
+the internals differ greatly. For more information, see the bcron homepage at |
85 |
+<uri>http://untroubled.org/bcron/</uri>. |
86 |
+</p> |
87 |
+ |
88 |
+<p> |
89 |
+Features of <c>sys-process/bcron</c>: |
90 |
+</p> |
91 |
+ |
92 |
+<ul> |
93 |
+ <li>Drop-in replacement for vixie-cron</li> |
94 |
+ <li>Multiprocess design</li> |
95 |
+ <li>Native daylight savings time support</li> |
96 |
+</ul> |
97 |
+ |
98 |
+</body> |
99 |
+</section> |
100 |
<section> |
101 |
<title>Anacron</title> |
102 |
<body> |
103 |
@@ -235,7 +261,7 @@ |
104 |
<p> |
105 |
Of course, you can choose not to use any system crontab at all. If you chose |
106 |
Dcron or Fcron, do <e>not</e> run <c>crontab /etc/crontab</c>. If you chose |
107 |
-vixie-cron, you should comment all lines in <path>/etc/crontab</path>. |
108 |
+vixie-cron or bcron, you should comment all lines in <path>/etc/crontab</path>. |
109 |
</p> |
110 |
|
111 |
<pre caption="Commenting all lines in /etc/crontab"> |
112 |
@@ -370,7 +396,7 @@ |
113 |
<ti><c>fcrontab -l</c></ti> |
114 |
</tr> |
115 |
<tr> |
116 |
- <ti>vixie-cron</ti> |
117 |
+ <ti>vixie-cron & bcron</ti> |
118 |
<ti><c>crontab -e</c></ti> |
119 |
<ti><c>crontab -r <e>-u [user]</e></c></ti> |
120 |
<ti><c>crontab <e>file</e></c></ti> |
121 |
@@ -588,7 +614,7 @@ |
122 |
<body> |
123 |
|
124 |
<p> |
125 |
-As mentioned earlier, all three of the available cron packages depend on |
126 |
+As mentioned earlier, all of the available cron packages depend on |
127 |
<c>sys-process/cronbase</c>. The cronbase package creates |
128 |
<path>/etc/cron.{hourly,daily,weekly,monthly}</path>, and a script called |
129 |
<c>run-crons</c>. You might have noticed that the default |
130 |
@@ -624,7 +650,7 @@ |
131 |
</ul> |
132 |
|
133 |
<note> |
134 |
-Again, it is useful to point out that Vixie cron automatically reads |
135 |
+Again, it is useful to point out that Vixie cron and bcron automatically read |
136 |
<path>/etc/crontab</path>, while dcron and fcron do not. Please read the <uri |
137 |
link="#systemtab">System crontab</uri> section to learn more about this. |
138 |
</note> |
139 |
|
140 |
|
141 |
|
142 |
-- |
143 |
gentoo-doc-cvs@l.g.o mailing list |