changes from Rick Macklem

[unix-history] / usr / src / usr.sbin / sendmail / doc / syslog.8

diff --git a/usr/src/usr.sbin/sendmail/doc/syslog.8 b/usr/src/usr.sbin/sendmail/doc/syslog.8
index c97f162..9741b74 100644 (file)
--- a/usr/src/usr.sbin/sendmail/doc/syslog.8
+++ b/usr/src/usr.sbin/sendmail/doc/syslog.8
@@ -1,5 +1,5 @@
 .TH SYSLOG 8
 .TH SYSLOG 8

-.\"    @(#)syslog.8    1.2             %G%
+.\"    @(#)syslog.8    4.2             %G%

 .SH NAME
 syslog \- log systems messages
 .SH SYNOPSIS
 .SH NAME
 syslog \- log systems messages
 .SH SYNOPSIS


@@ -24,7 +24,9 @@ Each message is one line.
 A message can contain a priority code,
 marked by a digit in angle braces
 at the beginning of the line.
 A message can contain a priority code,
 marked by a digit in angle braces
 at the beginning of the line.

-Priorities are defined in <syslog.h>, as follows:
+Priorities are defined in
+.RI < syslog.h >,
+as follows:

 .IP LOG_ALERT \w'LOG_WARNING'u+2n
 this priority should essentially never
 be used.  It applies only to messages that
 .IP LOG_ALERT \w'LOG_WARNING'u+2n
 this priority should essentially never
 be used.  It applies only to messages that


@@ -48,7 +50,7 @@ disk failures, etc.
 .IP LOG_CRIT
 such messages contain critical information,
 but which can not be classed as errors, for example,
 .IP LOG_CRIT
 such messages contain critical information,
 but which can not be classed as errors, for example,

-'su' attempts.
+`su' attempts.

 Messages of this priority and higher
 are typically logged on the system console.
 .IP LOG_WARNING
 Messages of this priority and higher
 are typically logged on the system console.
 .IP LOG_WARNING


@@ -56,7 +58,7 @@ issued when an abnormal condition has been
 detected, but recovery can take place.
 .IP LOG_NOTICE
 something that falls in the class of
 detected, but recovery can take place.
 .IP LOG_NOTICE
 something that falls in the class of

-"important information"; this class is informational
+``important information''; this class is informational

 but important enough that you don't want to throw
 it away casually.
 Messages without any priority assigned to them
 but important enough that you don't want to throw
 it away casually.
 Messages without any priority assigned to them


@@ -92,7 +94,7 @@ informed on SALERT level messages.
 For example, the configuration file:
 .nf
 
 For example, the configuration file:
 .nf
 

-       5*/dev/tty8
+       5*/dev/console

        8/usr/spool/adm/syslog
        3/usr/adm/critical
 
        8/usr/spool/adm/syslog
        3/usr/adm/critical
 


@@ -112,13 +114,16 @@ The users ``eric'', ``kridle'', and ``kalash''
 will be informed on any subalert messages.
 .PP
 The flags are:
 will be informed on any subalert messages.
 .PP
 The flags are:

-.IP \-m 0.5i
+.TP 0.5i
+.B \-m

 Set the mark interval to
 .I N
 (default 20 minutes).
 Set the mark interval to
 .I N
 (default 20 minutes).

-.IP \-f
+.TP
+.B \-f

 Specify an alternate configuration file.
 Specify an alternate configuration file.

-.IP \-d
+.TP
+.B \-d

 Turn on debugging (if compiled in).
 .PP
 To bring
 Turn on debugging (if compiled in).
 .PP
 To bring


@@ -147,20 +152,20 @@ containing a single line
 with its process id.
 This can be used to kill or reconfigure
 .I syslog.
 with its process id.
 This can be used to kill or reconfigure
 .I syslog.

-.PP
-.I Syslog
-can also be compiled to use
-.IR mpx (2)
-files instead of datagrams
-if you are running V7.
-In this case it creates and reads the file
-/dev/log.
+.\".PP
+.\".I Syslog
+.\"can also be compiled to use
+.\".IR mpx (2)
+.\"files instead of datagrams
+.\"if you are running V7.
+.\"In this case it creates and reads the file
+.\"/dev/log.

 .SH FILES
 /etc/syslog.conf \- the configuration file
 .br
 /etc/syslog.pid \- the process id
 .SH FILES
 /etc/syslog.conf \- the configuration file
 .br
 /etc/syslog.pid \- the process id

-.br
-/dev/log \- under V7, the mpx file
+.\".br
+.\"/dev/log \- under V7, the mpx file

 .SH BUGS
 LOG_ALERT and LOG_SUBALERT messages
 should only be allowed to privileged programs.
 .SH BUGS
 LOG_ALERT and LOG_SUBALERT messages
 should only be allowed to privileged programs.