docs/66963: [patch] handbook - a note on /etc/crontab

[platanthera]

>Number:         66963
>Category:       docs
>Synopsis:       [patch] handbook - a note on /etc/crontab
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 20 15:00:37 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator:     platanthera
>Release:        5.2.1 i386
>Organization:
>Environment:
>Description:
      6.6.1 Installing a Crontab
To install your freshly written crontab, just use the crontab utility. The most common usage is:
# crontab crontab

Apparently quite a number of users try to apply this approach to /etc/crontab. Therefore it should be explicitly warned not to do this. (I know that it's already in the FAQ)
>How-To-Repeat:
      read freebsd-users@ for some days
>Fix:
      patch for doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml

--- chapter.sgml.old    Tue May  4 22:51:58 2004
+++ chapter.sgml        Thu May 20 23:16:56 2004

@@ -549,6 +549,17 @@
        with an empty file.  When the file is saved, it will be
        automatically installed by the <command>crontab</command> command.
       </para>
+
+
+      <note>
+        <para>Changes in <filename>/etc/crontab</filename> are picked up by
+       <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum>
+       </citerefentry> automatically. Do NOT try to use <citerefentry>
+       <refentrytitle>crontab</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+       to update the system crontab, in the
+       <ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#ROOT-NOT-FOUND-CRON-ERRORS">
+       FAQ</ulink> there's an explanation why this doesn't work.</para>
+      </note>

     </sect2>
   </sect1>
>Release-Note:
>Audit-Trail:
>Unformatted: