1 '\" te

   2 .\" Copyright (C) 2008, Sun Microsystems, Inc. All Rights Reserved
   3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6 .TH SYSLOGD 1M "Oct 31, 2008"
   7 .SH NAME
   8 syslogd \- log system messages
   9 .SH SYNOPSIS
  10 .LP
  11 .nf
  12 \fB/usr/sbin/syslogd\fR [\fB-d\fR] [\fB-f\fR \fIconfigfile\fR] [\fB-m\fR \fImarkinterval\fR]
  13      [\fB-p\fR \fIpath\fR] [\fB-t\fR | \fB-T\fR]
  14 .fi
  15 
  16 .SH DESCRIPTION
  17 .sp
  18 .LP
  19 \fBsyslogd\fR reads and forwards system messages to the appropriate log files
  20 or users, depending upon the priority of a message and the system facility from
  21 which it originates. The configuration file \fB/etc/syslog.conf\fR (see
  22 \fBsyslog.conf\fR(4)) controls where messages are forwarded. \fBsyslogd\fR logs
  23 a mark (timestamp) message every \fImarkinterval\fR minutes (default \fB20\fR)
  24 at priority \fBLOG_INFO\fR to the facility whose name is given as \fBmark\fR in
  25 the \fBsyslog.conf\fR file.
  26 .sp

  45 As it starts up, \fBsyslogd\fR creates the file \fB/var/run/syslog.pid\fR, if
  46 possible, containing its process identifier (\fBPID\fR).
  47 .sp
  48 .LP
  49 If message \fBID\fR generation is enabled (see \fBlog\fR(7D)), each message
  50 will be preceded by an identifier in the following format: \fB[ID\fR \fImsgid
  51 facility\fR\fB\&.\fR\fIpriority\fR\fB]\fR. \fImsgid\fR is the message's numeric
  52 identifier described in \fBmsgid\fR(1M). \fIfacility\fR and \fIpriority\fR are
  53 described in \fBsyslog.conf\fR(4). \fB[ID 123456 kern.notice]\fR is an example
  54 of an identifier when message \fBID\fR generation is enabled.
  55 .sp
  56 .LP
  57 If the message originated in a loadable kernel module or driver, the kernel
  58 module's name (for example, \fBufs\fR) will be displayed instead of \fBunix\fR.
  59 See \fBEXAMPLES\fR for sample output from \fBsyslogd\fR with and without
  60 message \fBID\fR generation enabled.
  61 .sp
  62 .LP
  63 In an effort to reduce visual clutter, message \fBID\fRs are not displayed when
  64 writing to the console; message \fBID\fRs are only written to the log file.
  65 See .
  66 .sp
  67 .LP
  68 The \fB/etc/default/syslogd\fR file contains the following default parameter
  69 settings, which are in effect if neither the \fB-t\fR nor \fB-T\fR option is
  70 selected. See \fBFILES\fR.
  71 .sp
  72 .LP
  73 The recommended way to allow or disallow message logging is through the use of
  74 the service management facility (\fBsmf\fR(5)) property:
  75 .sp
  76 .in +2
  77 .nf
  78 svc:/system/system-log/config/log_from_remote
  79 .fi
  80 .in -2
  81 
  82 .sp
  83 .LP
  84 This property specifies whether remote messages are logged.
  85 \fBlog_from_remote=true\fR is equivalent to the \fB-t\fR command-line option

 135 .RE
 136 
 137 .sp
 138 .ne 2
 139 .na
 140 \fB\fB-p\fR \fIpath\fR\fR
 141 .ad
 142 .sp .6
 143 .RS 4n
 144 Specify an alternative log device name. The default is \fB/dev/log\fR.
 145 .RE
 146 
 147 .sp
 148 .ne 2
 149 .na
 150 \fB\fB-T\fR\fR
 151 .ad
 152 .sp .6
 153 .RS 4n
 154 Enable the \fBsyslogd\fR \fBUDP\fR port to turn on logging of remote messages.
 155 This is the default behavior. See .
 156 .RE
 157 
 158 .sp
 159 .ne 2
 160 .na
 161 \fB\fB-t\fR\fR
 162 .ad
 163 .sp .6
 164 .RS 4n
 165 Disable the \fBsyslogd\fR \fBUDP\fR port to turn off logging of remote
 166 messages. See .
 167 .RE
 168 
 169 .SH EXAMPLES
 170 .LP
 171 \fBExample 1 \fR\fBsyslogd\fR Output Without Message ID Generation Enabled
 172 .sp
 173 .LP
 174 The following example shows the output from \fBsyslogd\fR when message \fBID\fR
 175 generation \fBis not\fR enabled:
 176 
 177 .sp
 178 .in +2
 179 .nf
 180 Sep 29 21:41:18 cathy unix: alloc /: file system full
 181 .fi
 182 .in -2
 183 .sp
 184 
 185 .LP
 186 \fBExample 2 \fR\fBsyslogd\fR Output with ID generation Enabled

   1 '\" te
   2 .\" Copyright (c) 2013 Gary Mills
   3 .\" Copyright (C) 2008, Sun Microsystems, Inc. All Rights Reserved
   4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   7 .TH SYSLOGD 1M "Oct 17, 2013"
   8 .SH NAME
   9 syslogd \- log system messages
  10 .SH SYNOPSIS
  11 .LP
  12 .nf
  13 \fB/usr/sbin/syslogd\fR [\fB-d\fR] [\fB-f\fR \fIconfigfile\fR] [\fB-m\fR \fImarkinterval\fR]
  14      [\fB-p\fR \fIpath\fR] [\fB-t\fR | \fB-T\fR]
  15 .fi
  16 
  17 .SH DESCRIPTION
  18 .sp
  19 .LP
  20 \fBsyslogd\fR reads and forwards system messages to the appropriate log files
  21 or users, depending upon the priority of a message and the system facility from
  22 which it originates. The configuration file \fB/etc/syslog.conf\fR (see
  23 \fBsyslog.conf\fR(4)) controls where messages are forwarded. \fBsyslogd\fR logs
  24 a mark (timestamp) message every \fImarkinterval\fR minutes (default \fB20\fR)
  25 at priority \fBLOG_INFO\fR to the facility whose name is given as \fBmark\fR in
  26 the \fBsyslog.conf\fR file.
  27 .sp

  46 As it starts up, \fBsyslogd\fR creates the file \fB/var/run/syslog.pid\fR, if
  47 possible, containing its process identifier (\fBPID\fR).
  48 .sp
  49 .LP
  50 If message \fBID\fR generation is enabled (see \fBlog\fR(7D)), each message
  51 will be preceded by an identifier in the following format: \fB[ID\fR \fImsgid
  52 facility\fR\fB\&.\fR\fIpriority\fR\fB]\fR. \fImsgid\fR is the message's numeric
  53 identifier described in \fBmsgid\fR(1M). \fIfacility\fR and \fIpriority\fR are
  54 described in \fBsyslog.conf\fR(4). \fB[ID 123456 kern.notice]\fR is an example
  55 of an identifier when message \fBID\fR generation is enabled.
  56 .sp
  57 .LP
  58 If the message originated in a loadable kernel module or driver, the kernel
  59 module's name (for example, \fBufs\fR) will be displayed instead of \fBunix\fR.
  60 See \fBEXAMPLES\fR for sample output from \fBsyslogd\fR with and without
  61 message \fBID\fR generation enabled.
  62 .sp
  63 .LP
  64 In an effort to reduce visual clutter, message \fBID\fRs are not displayed when
  65 writing to the console; message \fBID\fRs are only written to the log file.
  66 See \fBEXAMPLES\fR.
  67 .sp
  68 .LP
  69 The \fB/etc/default/syslogd\fR file contains the following default parameter
  70 settings, which are in effect if neither the \fB-t\fR nor \fB-T\fR option is
  71 selected. See \fBFILES\fR.
  72 .sp
  73 .LP
  74 The recommended way to allow or disallow message logging is through the use of
  75 the service management facility (\fBsmf\fR(5)) property:
  76 .sp
  77 .in +2
  78 .nf
  79 svc:/system/system-log/config/log_from_remote
  80 .fi
  81 .in -2
  82 
  83 .sp
  84 .LP
  85 This property specifies whether remote messages are logged.
  86 \fBlog_from_remote=true\fR is equivalent to the \fB-t\fR command-line option

 136 .RE
 137 
 138 .sp
 139 .ne 2
 140 .na
 141 \fB\fB-p\fR \fIpath\fR\fR
 142 .ad
 143 .sp .6
 144 .RS 4n
 145 Specify an alternative log device name. The default is \fB/dev/log\fR.
 146 .RE
 147 
 148 .sp
 149 .ne 2
 150 .na
 151 \fB\fB-T\fR\fR
 152 .ad
 153 .sp .6
 154 .RS 4n
 155 Enable the \fBsyslogd\fR \fBUDP\fR port to turn on logging of remote messages.
 156 This is the default behavior. See \fBEXAMPLES\fR.
 157 .RE
 158 
 159 .sp
 160 .ne 2
 161 .na
 162 \fB\fB-t\fR\fR
 163 .ad
 164 .sp .6
 165 .RS 4n
 166 Disable the \fBsyslogd\fR \fBUDP\fR port to turn off logging of remote
 167 messages. See \fBEXAMPLES\fR.
 168 .RE
 169 
 170 .SH EXAMPLES
 171 .LP
 172 \fBExample 1 \fR\fBsyslogd\fR Output Without Message ID Generation Enabled
 173 .sp
 174 .LP
 175 The following example shows the output from \fBsyslogd\fR when message \fBID\fR
 176 generation \fBis not\fR enabled:
 177 
 178 .sp
 179 .in +2
 180 .nf
 181 Sep 29 21:41:18 cathy unix: alloc /: file system full
 182 .fi
 183 .in -2
 184 .sp
 185 
 186 .LP
 187 \fBExample 2 \fR\fBsyslogd\fR Output with ID generation Enabled