diff options
Diffstat (limited to 'usr/src/man/man8/syslogd.8')
| -rw-r--r-- | usr/src/man/man8/syslogd.8 | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/usr/src/man/man8/syslogd.8 b/usr/src/man/man8/syslogd.8 index dd268220f9..58f9afbbee 100644 --- a/usr/src/man/man8/syslogd.8 +++ b/usr/src/man/man8/syslogd.8 @@ -17,7 +17,7 @@ syslogd \- log system messages \fBsyslogd\fR reads and forwards system messages to the appropriate log files or users, depending upon the priority of a message and the system facility from which it originates. The configuration file \fB/etc/syslog.conf\fR (see -\fBsyslog.conf\fR(4)) controls where messages are forwarded. \fBsyslogd\fR logs +\fBsyslog.conf\fR(5)) controls where messages are forwarded. \fBsyslogd\fR logs a mark (timestamp) message every \fImarkinterval\fR minutes (default \fB20\fR) at priority \fBLOG_INFO\fR to the facility whose name is given as \fBmark\fR in the \fBsyslog.conf\fR file. @@ -44,11 +44,11 @@ As it starts up, \fBsyslogd\fR creates the file \fB/var/run/syslog.pid\fR, if possible, containing its process identifier (\fBPID\fR). .sp .LP -If message \fBID\fR generation is enabled (see \fBlog\fR(7D)), each message +If message \fBID\fR generation is enabled (see \fBlog\fR(4D)), each message will be preceded by an identifier in the following format: \fB[ID\fR \fImsgid facility\fR\fB\&.\fR\fIpriority\fR\fB]\fR. \fImsgid\fR is the message's numeric -identifier described in \fBmsgid\fR(1M). \fIfacility\fR and \fIpriority\fR are -described in \fBsyslog.conf\fR(4). \fB[ID 123456 kern.notice]\fR is an example +identifier described in \fBmsgid\fR(8). \fIfacility\fR and \fIpriority\fR are +described in \fBsyslog.conf\fR(5). \fB[ID 123456 kern.notice]\fR is an example of an identifier when message \fBID\fR generation is enabled. .sp .LP @@ -69,7 +69,7 @@ selected. See \fBFILES\fR. .sp .LP The recommended way to allow or disallow message logging is through the use of -the service management facility (\fBsmf\fR(5)) property: +the service management facility (\fBsmf\fR(7)) property: .sp .in +2 .nf @@ -298,9 +298,9 @@ Network services for each transport .RE .SH SEE ALSO -\fBlogger\fR(1), \fBsvcs\fR(1), \fBmsgid\fR(1M), \fBsvcadm\fR(1M), -\fBsvccfg\fR(1M), \fBsyslog\fR(3C), \fBsyslog.conf\fR(4), \fBattributes\fR(5), -\fBsignal.h\fR(3HEAD), \fBsmf\fR(5), \fBlog\fR(7D) +\fBlogger\fR(1), \fBsvcs\fR(1), \fBmsgid\fR(8), \fBsvcadm\fR(8), +\fBsvccfg\fR(8), \fBsyslog\fR(3C), \fBsyslog.conf\fR(5), \fBattributes\fR(7), +\fBsignal.h\fR(3HEAD), \fBsmf\fR(7), \fBlog\fR(4D) .SH NOTES The \fBmark\fR message is a system time stamp, and so it is only defined for the system on which \fBsyslogd\fR is running. It can not be forwarded to other @@ -326,7 +326,7 @@ window. .sp .LP The \fBsyslogd\fR service is managed by the service management facility, -\fBsmf\fR(5), under the service identifier: +\fBsmf\fR(7), under the service identifier: .sp .in +2 .nf @@ -338,11 +338,11 @@ The \fBsyslogd\fR service is managed by the service management facility, .sp .LP Administrative actions on this service, such as enabling, disabling, or -requesting restart, can be performed using \fBsvcadm\fR(1M). The service's +requesting restart, can be performed using \fBsvcadm\fR(8). The service's status can be queried using the \fBsvcs\fR(1) command. .sp .LP -When \fBsyslogd\fR is started by means of \fBsvcadm\fR(1M), if a value is +When \fBsyslogd\fR is started by means of \fBsvcadm\fR(8), if a value is specified for \fBLOG_FROM_REMOTE\fR in the \fB/etc/defaults/syslogd\fR file, the SMF property \fBsvc:/system/system-log/config/log_from_remote\fR is set to correspond to the \fBLOG_FROM_REMOTE\fR value and the @@ -351,7 +351,7 @@ correspond to the \fBLOG_FROM_REMOTE\fR value and the .sp .in +2 .nf -# LOG_FROM_REMOTE is now set using svccfg(1m), see syslogd(1m). +# LOG_FROM_REMOTE is now set using svccfg(8), see syslogd(8). .fi .in -2 |