From ddb9c022625e63515080e9a4ad69d363fd052760 Mon Sep 17 00:00:00 2001 From: Warren Block Date: Wed, 31 Oct 2012 02:41:03 +0000 Subject: [PATCH] Remove redundant words, fix title capitalization. --- .../books/handbook/config/chapter.xml | 69 +++++++++---------- 1 file changed, 34 insertions(+), 35 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.xml b/en_US.ISO8859-1/books/handbook/config/chapter.xml index 43f5b1ebab..2f9957e540 100644 --- a/en_US.ISO8859-1/books/handbook/config/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/config/chapter.xml @@ -256,8 +256,8 @@ implies this; it is configuration information for the rc* files. - An administrator should make entries in the - rc.conf file to override the default + An administrator should make entries in + rc.conf to override the default settings from /etc/defaults/rc.conf. The defaults file should not be copied verbatim to /etc - it contains @@ -269,8 +269,8 @@ applications to separate site-wide configuration from system-specific configuration in order to keep administration overhead down. The recommended approach is to place - system-specific configuration into the - /etc/rc.conf.local file. For + system-specific configuration into + /etc/rc.conf.local. For example: @@ -292,14 +292,14 @@ ifconfig_fxp0="inet 10.1.1.1/8" - The rc.conf file can then be + rc.confcan then be distributed to every system using rsync or a - similar program, while the rc.conf.local - file remains unique. + similar program, while rc.conf.local + remains unique. Upgrading the system using &man.sysinstall.8; or - make world will not overwrite the - rc.conf file, so system configuration + make world will not overwrite + rc.conf, so system configuration information will not be lost. @@ -349,8 +349,8 @@ ifconfig_fxp0="inet 10.1.1.1/8" -rw-r--r-- 1 root wheel 7980 May 20 1998 srm.conf -rw-r--r-- 1 root wheel 7933 May 20 1998 srm.conf.default - The file sizes show that only the - srm.conf file has been changed. A later + The file sizes show that only + srm.conf has been changed. A later update of the Apache port would not overwrite this changed file. @@ -439,8 +439,7 @@ run_rc_command "$1" command line arguments, inclusion of the default functions provided in /etc/rc.subr, compatibility with the &man.rcorder.8; utility and provides for easier - configuration via the rc.conf - file. + configuration via rc.conf. @@ -450,7 +449,7 @@ run_rc_command "$1" daemons, IMAP, etc. could be started using &man.inetd.8;. This involves installing the service utility from the Ports Collection with a configuration line added to - the /etc/inetd.conf file, or by + /etc/inetd.conf, or by uncommenting one of the current configuration lines. Working with inetd and its configuration is described in depth in the @@ -521,8 +520,8 @@ run_rc_command "$1" root. - Let us take a look at the /etc/crontab - file (the system crontab): + Let us take a look at /etc/crontab + (the system crontab): # /etc/crontab - root's crontab for &os; # @@ -593,11 +592,11 @@ HOME=/var/log These * characters mean first-last, and can be interpreted as every time. So, judging by this line, - it is apparent that the atrun command is + it is apparent that atrun is to be invoked by root every five minutes regardless of what day or month it is. For more - information on the atrun command, see the - &man.atrun.8; manual page. + information on atrun, see + &man.atrun.8;. Commands can have any number of flags passed to them; however, commands which extend to multiple lines need to be @@ -610,7 +609,7 @@ HOME=/var/log crontab file, although there is one thing different about this one. Field number six, where we specified the username, only exists in the system - /etc/crontab file. This field should be + /etc/crontab. This field should be omitted for individual user crontab files. @@ -728,7 +727,7 @@ $sshd_enable=YES The second line (# sshd) is the output - from the sshd command, not a + from sshd, not a root console. @@ -1275,7 +1274,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms You could also use the machine name instead of 192.168.1.2 if you have set - up the /etc/hosts file. + up /etc/hosts. @@ -1427,7 +1426,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255" - Configuring the system logger + <title>Configuring the System Logger, <application>syslogd</application> system logging @@ -1607,7 +1606,7 @@ cron.* /var/log/cron - Log management and rotation with + <title>Log Management and Rotation with <application>newsyslog</application> newsyslog @@ -1983,10 +1982,10 @@ kern.maxfiles: 2088 -> 5000 numbers, or booleans (a boolean being 1 for yes or a 0 for no). - If you want to set automatically some variables each time - the machine boots, add them to the - /etc/sysctl.conf file. For more - information see the &man.sysctl.conf.5; manual page and the + If you want to automatically set some variables each time + the machine boots, add them to + /etc/sysctl.conf. For more + information see the &man.sysctl.conf.5; manual page and . @@ -2018,8 +2017,8 @@ device_probe_and_attach: cbb0 attach returned 12 only. To overcome these situations a user can put &man.sysctl.8; OIDs in their local /boot/loader.conf. Default settings are - located in the /boot/defaults/loader.conf - file. + located in + /boot/defaults/loader.conf. Fixing the problem mentioned above would require a user to set in @@ -2425,8 +2424,8 @@ device_probe_and_attach: cbb0 attach returned 12 defaults by kern.maxusers may be individually overridden at boot-time or run-time in /boot/loader.conf (see the - &man.loader.conf.5; manual page or the - /boot/defaults/loader.conf file for + &man.loader.conf.5; manual page or + /boot/defaults/loader.conf for some hints) or as described elsewhere in this document. @@ -2894,7 +2893,7 @@ kern.maxvnodes: 100000 without doing a kernel rebuild. This has the advantage of making testing easier. Another reason is that starting ACPI after a system has been brought up - often doesn't work well. If you are experiencing problems, + often does not work well. If you are experiencing problems, you can disable ACPI altogether. This driver should not and can not be unloaded because the system bus uses it for various hardware interactions. @@ -3107,8 +3106,8 @@ kern.maxvnodes: 100000 In some cases, resuming from a suspend operation will cause the mouse to fail. A known work around is to add - hint.psm.0.flags="0x3000" to the - /boot/loader.conf file. If this does + hint.psm.0.flags="0x3000" to + /boot/loader.conf. If this does not work then please consider sending a bug report as described above.