Add a missing ")", use <envar> for environment variables,

mark up error messages with <errorname>.
This commit is contained in:
Martin Heinen 2003-08-23 11:50:41 +00:00
parent d18583bcc7
commit f091c36e76
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=17956

View file

@ -473,9 +473,9 @@ HOME=/var/log
<callout arearefs="co-env">
<para>First, the environment must be defined. The equals
(<literal>=</literal> character is used to define any environment
settings, as with this example where it is used for the <option>SHELL</option>,
<option>PATH</option>, and <option>HOME</option> options. If the shell line is
(<literal>=</literal>) character is used to define any environment
settings, as with this example where it is used for the <envar>SHELL</envar>,
<envar>PATH</envar>, and <envar>HOME</envar> options. If the shell line is
omitted, <command>cron</command> will use the default, which is
<command>sh</command>. If the <option>PATH</option> variable is
omitted, no default will be used and file locations will need to
@ -1028,7 +1028,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
the cable connections. Perhaps you may just need to get
another card.</para>
<para>At times, users see a few <quote>watchdog timeout</quote>
<para>At times, users see a few <errorname>watchdog timeout</errorname>
errors. The first thing to do here is to check your network
cable. Many cards require a PCI slot which supports Bus
Mastering. On some old motherboards, only one PCI slot allows
@ -1036,7 +1036,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
motherboard documentation to determine if that may be the
problem.</para>
<para><quote>No route to host</quote> messages occur if the
<para><errorname>No route to host</errorname> messages occur if the
system is unable to route a packet to the destination host.
This can happen if no default route is specified, or if a
cable is unplugged. Check the output of <command>netstat
@ -1044,7 +1044,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
you are trying to reach. If there is not, read on to <xref
linkend="advanced-networking">.</para>
<para><quote>ping: sendto: Permission denied</quote> error
<para><errorname>ping: sendto: Permission denied</errorname> error
messages are often caused by a misconfigured firewall. If
<command>ipfw</command> is enabled in the kernel but no rules
have been defined, then the default policy is to deny all