diff options
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/config/chapter.sgml')
| -rw-r--r-- | en_US.ISO8859-1/books/handbook/config/chapter.sgml | 58 |
1 files changed, 6 insertions, 52 deletions
diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.sgml b/en_US.ISO8859-1/books/handbook/config/chapter.sgml index e9953889fd..efa28ae87d 100644 --- a/en_US.ISO8859-1/books/handbook/config/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/config/chapter.sgml @@ -441,29 +441,8 @@ exit 0 <filename>crontab</filename> files store information about specific functions which <command>cron</command> is supposed to perform at certain times.</para> - - <para>The <command>cron</command> utility uses two different - types of configuration files, the system crontab and user crontabs. The - only difference between these two formats is the sixth field. In the - system crontab, the sixth field is the name of a user for the command - to run as. This gives the system crontab the ability to run commands - as any user. In a user crontab, the sixth field is the command to run, - and all commands run as the user who created the crontab; this is an - important security feature.</para> - - <note> - <para>User crontabs allow individual users to schedule tasks without the - need for root privileges. Commands in a user's crontab run with the - permissions of the user who owns the crontab.</para> - <para>The root user can have a user crontab just like - any other user. This one is different from - <filename>/etc/crontab</filename> (the system crontab). Because of the - system crontab, there's usually no need to create a user crontab - for root.</para> - </note> - <para>Let us take a look at the <filename>/etc/crontab</filename> file - (the system crontab):</para> + <para>Let us take a look at the <filename>/etc/crontab</filename> file:</para> <programlisting># /etc/crontab - root's crontab for &os; @@ -552,30 +531,16 @@ HOME=/var/log <sect2 id="configtuning-installcrontab"> <title>Installing a Crontab</title> - <important> - <para>You must not use the procedure described here to - edit/install the system crontab. Simply use your favorite - editor: the <command>cron</command> utility will notice that the file - has changed and immediately begin using the updated version. - See - <ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#ROOT-NOT-FOUND-CRON-ERRORS"> - this FAQ entry </ulink> for more information.</para> - </important> - - <para>To install a freshly written user - <filename>crontab</filename>, first use your favorite editor to create - a file in the proper format, and then use the + <para>To install your freshly written + <filename>crontab</filename>, just use the <command>crontab</command> utility. The most common usage is:</para> - <screen>&prompt.user; <userinput>crontab crontab-file</userinput></screen> - - <para>In this example, <filename>crontab-file</filename> is the filename - of a <filename>crontab</filename> that was previously created.</para> + <screen>&prompt.root; <userinput>crontab crontab</userinput></screen> <para>There is also an option to list installed - <filename>crontab</filename> files: just pass the - <option>-l</option> option to <command>crontab</command> and look + <filename>crontab</filename> files, just pass the + <option>-l</option> to <command>crontab</command> and look over the output.</para> <para>For users who wish to begin their own crontab file from scratch, @@ -584,11 +549,6 @@ HOME=/var/log with an empty file. When the file is saved, it will be automatically installed by the <command>crontab</command> command. </para> - - <para>If you later want to remove your user <filename>crontab</filename> - completely, use <command>crontab</command> with the <option>-r</option> - option. - </para> </sect2> </sect1> @@ -2380,12 +2340,6 @@ device_probe_and_attach: cbb0 attach returned 12</screen> <sect2 id="ACPI-submitdebug"> <title>Submitting Debugging Information</title> - <note> - <para>Before submitting a problem, be sure you are running the latest - <acronym>BIOS</acronym> version and, if available, embedded - controller firmware version.</para> - </note> - <para>For those of you that want to submit a problem right away, please send the following information to <ulink url="mailto:freebsd-acpi@FreeBSD.org"> |