Print this page 
4211 Some syslog facility names and symbols are missing
3232 syslogd shouldn't sync after each LOG_KERN line
1762 Syslogd man page: missing reference.
Split Close
Expand all
Collapse all
          --- old/usr/src/man/man1m/syslogd.1m
          +++ new/usr/src/man/man1m/syslogd.1m
   1    1  '\" te
        2 +.\" Copyright (c) 2013 Gary Mills
   2    3  .\" Copyright (C) 2008, Sun Microsystems, Inc. All Rights Reserved
   3    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.
   4    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.
   5    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]
   6      -.TH SYSLOGD 1M "Oct 31, 2008"
        7 +.TH SYSLOGD 1M "Oct 17, 2013"
   7    8  .SH NAME
   8    9  syslogd \- log system messages
   9   10  .SH SYNOPSIS
  10   11  .LP
  11   12  .nf
  12   13  \fB/usr/sbin/syslogd\fR [\fB-d\fR] [\fB-f\fR \fIconfigfile\fR] [\fB-m\fR \fImarkinterval\fR]
  13   14       [\fB-p\fR \fIpath\fR] [\fB-t\fR | \fB-T\fR]
  14   15  .fi
  15   16  
  16   17  .SH DESCRIPTION
↓ open down ↓ 38 lines elided ↑ open up ↑ 
  55   56  .sp
  56   57  .LP
  57   58  If the message originated in a loadable kernel module or driver, the kernel
  58   59  module's name (for example, \fBufs\fR) will be displayed instead of \fBunix\fR.
  59   60  See \fBEXAMPLES\fR for sample output from \fBsyslogd\fR with and without
  60   61  message \fBID\fR generation enabled.
  61   62  .sp
  62   63  .LP
  63   64  In an effort to reduce visual clutter, message \fBID\fRs are not displayed when
  64   65  writing to the console; message \fBID\fRs are only written to the log file.
  65      -See .
       66 +See \fBEXAMPLES\fR.
  66   67  .sp
  67   68  .LP
  68   69  The \fB/etc/default/syslogd\fR file contains the following default parameter
  69   70  settings, which are in effect if neither the \fB-t\fR nor \fB-T\fR option is
  70   71  selected. See \fBFILES\fR.
  71   72  .sp
  72   73  .LP
  73   74  The recommended way to allow or disallow message logging is through the use of
  74   75  the service management facility (\fBsmf\fR(5)) property:
  75   76  .sp
↓ open down ↓ 69 lines elided ↑ open up ↑ 
 145  146  .RE
 146  147  
 147  148  .sp
 148  149  .ne 2
 149  150  .na
 150  151  \fB\fB-T\fR\fR
 151  152  .ad
 152  153  .sp .6
 153  154  .RS 4n
 154  155  Enable the \fBsyslogd\fR \fBUDP\fR port to turn on logging of remote messages.
 155      -This is the default behavior. See .
      156 +This is the default behavior. See \fBEXAMPLES\fR.
 156  157  .RE
 157  158  
 158  159  .sp
 159  160  .ne 2
 160  161  .na
 161  162  \fB\fB-t\fR\fR
 162  163  .ad
 163  164  .sp .6
 164  165  .RS 4n
 165  166  Disable the \fBsyslogd\fR \fBUDP\fR port to turn off logging of remote
 166      -messages. See .
      167 +messages. See \fBEXAMPLES\fR.
 167  168  .RE
 168  169  
 169  170  .SH EXAMPLES
 170  171  .LP
 171  172  \fBExample 1 \fR\fBsyslogd\fR Output Without Message ID Generation Enabled
 172  173  .sp
 173  174  .LP
 174  175  The following example shows the output from \fBsyslogd\fR when message \fBID\fR
 175  176  generation \fBis not\fR enabled:
 176  177
↓ open down ↓ 200 lines elided ↑ open up ↑ 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX