syslogd(8) 맨 페이지 - 윈디하나의 솔라나라


맨 페이지 이름


System Administration Commands                                      syslogd(8)

       syslogd - log system messages

       /usr/sbin/syslogd [-d] [-f configfile] [-m markinterval]
            [-p path] [-t | -T]

       syslogd 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 /etc/sys‐
       log.conf (see syslog.conf(5)) controls where  messages  are  forwarded.
       syslogd  logs  a  mark  (timestamp)  message every markinterval minutes
       (default 20) at priority LOG_INFO to the facility whose name  is  given
       as mark in the syslog.conf file.

       A  system  message consists of a single line of text, which may be pre‐
       fixed with a priority code number enclosed in angle-brackets (<>); pri‐
       orities are defined in <sys/syslog.h>.

       syslogd  reads  from  the  STREAMS  log  driver, /dev/log, and from any
       transport  provider  specified   in   /etc/netconfig,   /etc/net/trans‐
       port/hosts, and /etc/net/transport/services.

       syslogd reads the configuration file when it starts up, and again when‐
       ever it receives a HUP signal (see signal.h(3HEAD), at  which  time  it
       also closes all files it has open, re-reads its configuration file, and
       then opens only the log files that are listed  in  that  file.  syslogd
       exits when it receives a TERM signal.

       As  it starts up, syslogd creates the file /var/run/, if pos‐
       sible, containing its process identifier (PID).

       If message ID generation is enabled (see log(4D)), each message will be
       preceded  by  an  identifier in the following format: [ID  msgid facil‐
       ity.priority]. msgid is the message's numeric identifier  described  in
       msgid(8).  facility  and  priority are described in syslog.conf(5). [ID
       123456 kern.notice] is an example of an identifier when message ID gen‐
       eration is enabled.

       If  the  message  originated in a loadable kernel module or driver, the
       kernel module's name (for example, ufs) will be  displayed  instead  of
       unix. See EXAMPLES for sample output from syslogd with and without mes‐
       sage ID generation enabled.

       In an effort to reduce visual clutter, message IDs  are  not  displayed
       when  writing  to  the console; message IDs are only written to the log
       file. See EXAMPLES.

       The /etc/default/syslogd file contains the default parameter  settings,
       which are in effect if neither the -t nor -T option is selected.

       The recommended way to allow or disallow message logging is through the
       use of the service management facility (smf(7)) property:


       This  property  specifies   whether   remote   messages   are   logged.
       log_from_remote=true  is  equivalent  to the -t command-line option and
       false is equivalent to the -T command-line option.  The  default  value
       for -log_from_remote is false. See NOTES, below.


           Specifies whether remote messages are logged. LOG_FROM_REMOTE=NO is
           equivalent to the -t command-line option.  The  default  value  for
           LOG_FROM_REMOTE is YES.

       The following options are supported:


           Turn on debugging. This option should only be used interactively in
           a root shell once the system is in multi-user mode. It  should  not
           be used in the system start-up scripts, as this will cause the sys‐
           tem to hang at the point where syslogd is started.

       -f configfile

           Specify an alternate configuration file.

       -m markinterval

           Specify an interval, in minutes, between mark messages.

       -p path

           Specify an alternative log device name. The default is /dev/log.


           Enable the syslogd  UDP port to turn on logging of remote messages.
           This is the default behavior.


           Disable  the  syslogd   UDP port to turn off logging of remote mes‐

       Example 1 syslogd Output Without Message ID Generation Enabled

       The following example shows the output from  syslogd  when  message  ID
       generation is not enabled:

         Sep 29 21:41:18 cathy unix: alloc /: file system full

       Example 2 syslogd Output with ID generation Enabled

       The  following  example  shows  the output from syslogd when message ID
       generation is enabled. The message ID is displayed when writing to  log

         Sep 29 21:41:18 cathy ufs: [ID 845546 kern.notice]
                                             alloc /: file system full

       Example 3 syslogd Output with ID Generation Enabled

       The  following  example  shows  the output from syslogd when message ID
       generation is enabled when writing to the console. Even though  message
       ID is enabled, the message ID is not displayed at the console.

         Sep 29 21:41:18 cathy ufs: alloc /: file system full

       Example 4 Enabling Acceptance of UDP Messages from Remote Systems

       The  following  commands  enable  syslogd to accept entries from remote

         # svccfg -s svc:/system/system-log setprop config/log_from_remote = true
         # svcadm restart svc:/system/system-log


           Configuration file


           Process ID


           Contains default settings. You can override some of the settings by
           command-line options.


           STREAMS log driver


           Transport providers available on the system


           Network hosts for each transport


           Network services for each transport

       See attributes(7) for descriptions of the following attributes:

       tab()  box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
       TRIBUTE VALUE _ Availabilitysystem/core-os

       logger(1),  svcs(1),   syslog(3C),   signal.h(3HEAD),   log(4D),   sys‐
       log.conf(5), attributes(7), smf(7), msgid(8), svcadm(8), svccfg(8)

       The  mark message is a system time stamp, and so it is only defined for
       the system on which syslogd is running. It  can  not  be  forwarded  to
       other systems.

       When  syslogd receives a HUP signal, it attempts to complete outputting
       pending messages, and close all log files to which it is currently log‐
       ging  messages.  If, for some reason, one (or more) of these files does
       not close within a generous grace period, syslogd discards the  pending
       messages,  forcibly  closes these files, and starts reconfiguration. If
       this shutdown procedure is disturbed by an unexpected error and syslogd
       cannot  complete  reconfiguration,  syslogd sends a mail message to the
       superuser on the current system stating that  it  has  shut  down,  and

       Care  should  be  taken  to ensure that each window displaying messages
       forwarded by syslogd (especially console windows) is run in the  system
       default  locale (which is syslogd's locale). If this advice is not fol‐
       lowed, it is possible for a syslog message to alter the  terminal  set‐
       tings for that window, possibly even allowing remote execution of arbi‐
       trary commands from that window.

       The syslogd service is managed  by  the  service  management  facility,
       smf(7), under the service identifier:


       Administrative actions on this service, such as enabling, disabling, or
       requesting restart, can be performed  using  svcadm(8).  The  service's
       status can be queried using the svcs(1) command.

       When  syslogd is started by means of svcadm(8), if a value is specified
       for LOG_FROM_REMOTE in the /etc/defaults/syslogd file, the SMF property
       svc:/system/system-log/config/log_from_remote  is  set to correspond to
       the LOG_FROM_REMOTE value and the /etc/default/syslogd file is modified
       to  replace  the  LOG_FROM_REMOTE specification with the following com‐

         # LOG_FROM_REMOTE is now set using svccfg(8), see syslogd(8).

       If    neither    LOG_FROM_REMOTE    nor     svc:/system/system-log/con‐
       fig/log_from_remote are defined, the default is to log remote messages.

       On  installation,  the  initial  value  of  svc:/system/system-log/con‐
       fig/log_from_remote is false.

Oracle Solaris 11.4               14 Nov 2011                       syslogd(8)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.