os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update the root-not-found-cron-error entry.

Browse source 
PR:		docs/25456
Submitted by:	Mike Meyer <mwm@mired.org>
This commit is contained in:
Nik Clayton 2001-02-28 22:47:51 +00:00
parent 0145e385e8
commit a5998db85c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=8863
2 changed files with 34 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.145 2001/02/24 12:18:04 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.146 2001/02/26 21:51:48 nik Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -5246,13 +5246,22 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
which &man.crontab.1; updates (the &man.crontab.5; manual
page explains the differences in more detail).</para>
<para>If this is what you did, you should delete the
<filename>/var/cron/tabs/root</filename>, since it will
simply be a copy of <filename>/etc/crontab</filename>,
in the wrong format. Next time, when you edit
<filename>/etc/crontab</filename>, you should not do
anything to inform &man.cron.8; of the changes, since it
will notice them automatically.</para>
<para>If this is what you did, the extra crontab is simply a
copy of <filename>/etc/crontab</filename> in the wrong
format it. Delete it with the command:</para>
<screen>&prompt.root; <userinput>crontab -r</userinput></screen>
<para>Next time, when you edit
<filename>/etc/crontab</filename>, you should not do
anything to inform &man.cron.8; of the changes, since it
will notice them automatically.</para>
<para>If you want something to be run once per day, week, or
month, it's probably better to add shell scripts
<filename>/usr/local/etc/periodic</filename>, and let the
&man.periodic.8; command run from the system cron schedule
it with the other periodic system tasks.</para>
<para>The actual reason for the error is that the system
crontab has an extra field, specifying which user to run the

25
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.145 2001/02/24 12:18:04 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.146 2001/02/26 21:51:48 nik Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -5246,13 +5246,22 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
which &man.crontab.1; updates (the &man.crontab.5; manual
page explains the differences in more detail).</para>
<para>If this is what you did, you should delete the
<filename>/var/cron/tabs/root</filename>, since it will
simply be a copy of <filename>/etc/crontab</filename>,
in the wrong format. Next time, when you edit
<filename>/etc/crontab</filename>, you should not do
anything to inform &man.cron.8; of the changes, since it
will notice them automatically.</para>
<para>If this is what you did, the extra crontab is simply a
copy of <filename>/etc/crontab</filename> in the wrong
format it. Delete it with the command:</para>
<screen>&prompt.root; <userinput>crontab -r</userinput></screen>
<para>Next time, when you edit
<filename>/etc/crontab</filename>, you should not do
anything to inform &man.cron.8; of the changes, since it
will notice them automatically.</para>
<para>If you want something to be run once per day, week, or
month, it's probably better to add shell scripts
<filename>/usr/local/etc/periodic</filename>, and let the
&man.periodic.8; command run from the system cron schedule
it with the other periodic system tasks.</para>
<para>The actual reason for the error is that the system
crontab has an extra field, specifying which user to run the