svn commit: r41664 - in projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook: config network-servers
Tom Rhodes
trhodes at FreeBSD.org
Sat May 18 19:56:00 UTC 2013
Author: trhodes
Date: Sat May 18 19:55:59 2013
New Revision: 41664
URL: http://svnweb.freebsd.org/changeset/doc/41664
Log:
Mark up syslogd and newsyslogd in <command> tags in the
section titles.
Add an introduction to the tuning disks chapter.
Modified:
projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml
projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml
Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml
==============================================================================
--- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Sat May 18 18:24:11 2013 (r41663)
+++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Sat May 18 19:55:59 2013 (r41664)
@@ -1362,7 +1362,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n
</sect1info>
<title>Configuring the System Logger,
- &man.syslogd.8;</title>
+ <command>syslogd</command></title>
<indexterm><primary>system logging</primary></indexterm>
<indexterm><primary>syslog</primary></indexterm>
@@ -1383,7 +1383,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n
linkend="network-syslogd"/>.</para>
<sect2>
- <title>Using &man.syslogd.8;</title>
+ <title>Using <command>syslogd</command></title>
<para>In the default &os; configuration, &man.syslogd.8; is
started at boot. This is controlled by the variable
@@ -1401,7 +1401,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n
</sect2>
<sect2>
- <title>Configuring &man.syslogd.8;</title>
+ <title>Configuring <command>syslogd</command></title>
<indexterm><primary>syslog.conf</primary></indexterm>
@@ -1541,7 +1541,7 @@ cron.*
<sect2>
<title>Log Management and Rotation with
- &man.newsyslog.8;</title>
+ <command>newsyslog</command></title>
<indexterm><primary>newsyslog</primary></indexterm>
<indexterm><primary>newsyslog.conf</primary></indexterm>
@@ -1563,7 +1563,7 @@ cron.*
<sect3>
<title>Configuring
- &man.newsyslog.8;</title>
+ <command>newsyslog</command></title>
<para>To know which actions to take, &man.newsyslog.8; reads
its configuration file, by default
@@ -1959,6 +1959,19 @@ device_probe_and_attach: cbb0 attach ret
<sect1 id="configtuning-disk">
<title>Tuning Disks</title>
+ <para>The following section will discuss various tuning
+ mechanisms and options which may be applied to disk
+ devices. In many cases, disks with mechanical parts,
+ such as <acronym>SCSI</acronym> drives, will be the bottle
+ neck driving down the overall system performance. While
+ a solution is to install a drive without mechanical parts,
+ such as a solid state drive, mechanical drives are not
+ going away anytime in the near future. When tuning disks,
+ it is advisable to utilize the features of the &man.iostat.8;
+ command to test various changes to the system. This
+ command will allow the user to obtain valuable information
+ on system <acronym>IO</acronym>.</para>
+
<sect2>
<title>Sysctl Variables</title>
Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml
==============================================================================
--- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat May 18 18:24:11 2013 (r41663)
+++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat May 18 19:55:59 2013 (r41664)
@@ -5682,7 +5682,7 @@ driftfile /var/db/ntp.drift</programlist
<para>Centralized logging to a specific logging host can reduce
some of the administrative burden of log file administration.
- Log file aggregation, merging and rotation can be configured in
+ Log file aggregation, merging and rotation may be configured in
one location, using the native tools of &os;, such as
&man.syslogd.8; and &man.newsyslog.8;. In the following example
configuration, host <hostid>A</hostid>, named <hostid
@@ -5716,15 +5716,15 @@ driftfile /var/db/ntp.drift</programlist
</listitem>
<listitem>
- <para>syslogd has been configured to accept remote messages
- from client machines;</para>
+ <para><command>syslogd</command> has been configured to
+ accept remote messages from client machines;</para>
</listitem>
<listitem>
- <para>The syslogd server and all client machines must have
- valid entries for both forward and reverse
- <acronym>DNS</acronym>, or be properly configured in
- <filename>/etc/hosts</filename>.</para>
+ <para>The <command>syslogd</command> server and all client
+ machines must have valid entries for both forward and
+ reverse <acronym>DNS</acronym>, or be properly configured
+ in <filename>/etc/hosts</filename>.</para>
</listitem>
</itemizedlist>
@@ -5770,13 +5770,14 @@ syslogd_flags="-a logclient.example.com
does not matter, but &man.touch.1; works great for situations
such as this:</para>
- <screen>&prompt.root; <userinput>touch <filename>/var/log/logclient.log</filename></userinput></screen>
+ <screen>&prompt.root; <userinput><command>touch</command>
+ <filename>/var/log/logclient.log</filename></userinput></screen>
<para>At this point, the <command>syslogd</command> daemon
should be restarted and verified:</para>
- <screen>&prompt.root; <userinput>service syslogd restart</userinput>
-&prompt.root; <userinput>pgrep syslog</userinput></screen>
+ <screen>&prompt.root; <userinput>service <command>syslogd</command> restart</userinput>
+&prompt.root; <userinput><command>pgrep</command> syslog</userinput></screen>
<para>If a <acronym>PID</acronym> is returned, the server has
been restarted successfully, and client configuration may
@@ -5851,13 +5852,14 @@ syslogd_flags="-s -v -v"</programlisting
<para>Once added, <command>syslogd</command> must be restarted
for the changes to take effect:</para>
- <screen>&prompt.root; <userinput>service syslogd restart</userinput></screen>
+ <screen>&prompt.root; <userinput>service <command>syslogd</command> restart</userinput></screen>
<para>To test that log messages are being sent across the
network, use &man.logger.1; on the client to send a message to
<command>syslogd</command>:</para>
- <screen>&prompt.root; <userinput>logger "<replaceable>Test message from logclient</replaceable>"</userinput></screen>
+ <screen>&prompt.root; <userinput><command>logger</command>
+ "<replaceable>Test message from logclient</replaceable>"</userinput></screen>
<para>This message should now exist both in
<filename>/var/log/messages</filename> on the client, and
@@ -5888,7 +5890,7 @@ syslogd_flags="-s -v -v"</programlisting
<programlisting>syslogd_flags="-d -a logclien.example.com -v -v"</programlisting>
- <screen>&prompt.root; <userinput>service syslogd restart</userinput></screen>
+ <screen>&prompt.root; <userinput>service <command>syslogd</command> restart</userinput></screen>
<para>Debugging data similar to the following will flash on the
screen immediately after the restart:</para>
@@ -5913,7 +5915,7 @@ rejected in rule 0 due to name mismatch.
<literal>logclien</literal>. After the proper alterations
are made, a restart is issued with expected results:</para>
- <screen>&prompt.root; <userinput>service syslogd restart</userinput>
+ <screen>&prompt.root; <userinput>service <command>syslogd</command> restart</userinput>
logmsg: pri 56, flags 4, from logserv.example.com, msg syslogd: restart
syslogd: restarted
logmsg: pri 6, flags 4, from logserv.example.com, msg syslogd: kernel boot file is /boot/kernel/kernel
More information about the svn-doc-projects
mailing list