From owner-svn-doc-all@FreeBSD.ORG Mon May 5 20:28:47 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EEAED2DB; Mon, 5 May 2014 20:28:46 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D003130D; Mon, 5 May 2014 20:28:46 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s45KSkD6059758; Mon, 5 May 2014 20:28:46 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s45KSkGO059756; Mon, 5 May 2014 20:28:46 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405052028.s45KSkGO059756@svn.freebsd.org> From: Dru Lavigne Date: Mon, 5 May 2014 20:28:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44767 - head/en_US.ISO8859-1/books/handbook/config X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2014 20:28:47 -0000 Author: dru Date: Mon May 5 20:28:46 2014 New Revision: 44767 URL: http://svnweb.freebsd.org/changeset/doc/44767 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/config/chapter.xml Mon May 5 19:49:44 2014 (r44766) +++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml Mon May 5 20:28:46 2014 (r44767) @@ -232,30 +232,29 @@ run_rc_command "$1" configuration - One of the most useful utilities in &os; is cron. - This utility runs in the background and regularly checks + One of the most useful utilities in &os; is + cron. This utility runs in the + background and regularly checks /etc/crontab for tasks to execute and - searches /var/cron/tabs for custom - crontab files. These files are used to schedule - tasks which cron runs at the - specified times. Each entry in a crontab defines a task to run - and is known as a cron job. - - Two different types of configuration files are used: - the system crontab, which should not be modified, and user - crontabs, which can be created and edited as needed. The format - used by these files is documented in &man.crontab.5;. The - format of the system crontab, /etc/crontab - includes a who column which does not exist in - user crontabs. In the system crontab, - cron runs the command as - the user specified in this column. In a user - crontab, all commands run as the user who - created the crontab. - - User crontabs allow - individual users to schedule their own tasks. The root user + searches /var/cron/tabs for custom crontab + files. These files are used to schedule tasks which + cron runs at the specified times. + Each entry in a crontab defines a task to run and is known as a + cron job. + + Two different types of configuration files are used: the + system crontab, which should not be modified, and user crontabs, + which can be created and edited as needed. The format used by + these files is documented in &man.crontab.5;. The format of the + system crontab, /etc/crontab includes a + who column which does not exist in user + crontabs. In the system crontab, + cron runs the command as the user + specified in this column. In a user crontab, all commands run + as the user who created the crontab. + + User crontabs allow individual users to schedule their own + tasks. The root user can also have a user crontab which can be used to schedule tasks that do not exist in the system crontab. @@ -276,13 +275,12 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin - Lines that begin - with the # character are comments. A - comment can be placed in the file as a reminder of what and - why a desired action is performed. Comments cannot be on - the same line as a command or else they will be interpreted - as part of the command; they must be on a new line. Blank - lines are ignored. + Lines that begin with the # character + are comments. A comment can be placed in the file as a + reminder of what and why a desired action is performed. + Comments cannot be on the same line as a command or else + they will be interpreted as part of the command; they must + be on a new line. Blank lines are ignored. @@ -290,45 +288,43 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin define any environment settings. In this example, it is used to define the SHELL and PATH. If the SHELL is - omitted, cron will use the default Bourne shell. - If the PATH is omitted, the full path must be given to the - command or script to run. + omitted, cron will use the + default Bourne shell. If the PATH is + omitted, the full path must be given to the command or + script to run. - This line defines the seven fields used in a system crontab: - minute, - hour, mday, - month, wday, - who, and command. - The - minute field is the time in minutes when the - specified command will be run, the hour is - the hour when the specified command will be run, the - mday is the day of the month, - month is the month, and - wday is the day of the week. + This line defines the seven fields used in a system + crontab: minute, hour, + mday, month, + wday, who, and + command. The minute + field is the time in minutes when the specified command will + be run, the hour is the hour when the + specified command will be run, the mday + is the day of the month, month is the + month, and wday is the day of the week. These fields must be numeric values, representing the twenty-four hour clock, or a *, representing all values for that field. The who field only exists in the system - crontab and specifies which user the command - should be run as. The last field is the command to be - executed. + crontab and specifies which user the command should be run + as. The last field is the command to be executed. - This entry defines the values for this cron job. - The */5, followed - by several more * characters, specifies that + This entry defines the values for this cron job. The + */5, followed by several more + * characters, specifies that /usr/libexec/atrun is invoked by root every five minutes of every hour, of every day and day of the week, of every month. - Commands can include any number of switches. - However, commands which extend to multiple lines need to be - broken with the backslash \ continuation + Commands can include any number of switches. However, + commands which extend to multiple lines need to be broken + with the backslash \ continuation character. @@ -346,30 +342,30 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin an empty file. Once a user creates a crontab, this command will open that file for editing. - It is useful to add these lines to the top of the crontab - file in order to set the environment variables and to remember - the meanings of the fields in the crontab: - - SHELL=/bin/sh + It is useful to add these lines to the top of the crontab + file in order to set the environment variables and to remember + the meanings of the fields in the crontab: + + SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin # Order of crontab fields # minute hour mday month wday command - Then add a line for each command or script to run, - specifying the time to run the command. This example runs the - specified custom Bourne shell script every day at two in the - afternoon. Since the path to the script is not specified in - PATH, the full path to the script is - given: - - 0 14 * * * /usr/home/dru/bin/mycustomscript.sh - - - Before using a custom script, make sure it is executable - and test that it works as intended from the command line. - This is especially important if the script includes any - commands that deletes files using wildcards. - + Then add a line for each command or script to run, + specifying the time to run the command. This example runs the + specified custom Bourne shell script every day at two in the + afternoon. Since the path to the script is not specified in + PATH, the full path to the script is + given: + + 0 14 * * * /usr/home/dru/bin/mycustomscript.sh + + + Before using a custom script, make sure it is executable + and test that it works as intended from the command line. + This is especially important if the script includes any + commands that deletes files using wildcards. + When finished editing the crontab, save the file. It will automatically be installed and @@ -381,10 +377,9 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin 0 14 * * * /usr/home/dru/bin/mycustomscript.sh To remove all of the cron jobs in a user crontab: - + &prompt.user; crontab -l remove crontab for dru? y - @@ -654,14 +649,14 @@ ifconfig_fxp0="inet 10.1.1.1/8" - The drivers for common NICs are - already present in the GENERIC kernel, - meaning the NIC should be probed during boot. - The system's boot messages can be viewed by typing + The drivers for common NICs are already + present in the GENERIC kernel, meaning + the NIC should be probed during boot. The + system's boot messages can be viewed by typing more /var/run/dmesg.boot and using the spacebar to scroll through the text. In this example, two - Ethernet NICs using the - &man.dc.4; driver are present on the system: + Ethernet NICs using the &man.dc.4; driver + are present on the system: dc0: <82c169 PNIC 10/100BaseTX> port 0xa000-0xa0ff mem 0xd3800000-0xd38 000ff irq 15 at device 11.0 on pci0