Installation guide

daemons are started. You can also specify options with the command that
starts the daemons. Refer to the init
(8) reference page for more
information.
13.2.3.1 The syslogd Daemon
You must ensure that the syslogd daemon is started by the init
program. If the syslogd daemon is not started or if you want to specify
options with the command that starts the syslogd daemon, you must edit
the /sbin/init.d/syslog file and either include or modify the syslogd
command line. Note that you can also invoke the command manually.
The command that starts the syslogd daemon has the following syntax:
/usr/sbin/syslogd
[-d][-f config_file][-m mark_interval]
Refer to the syslogd(8) reference page for information about command
options.
_______________________ Note _______________________
You must ensure that the /var/adm directory is mounted, or the
syslogd daemon will not work correctly.
The syslogd daemon reads messages from the following:
• The Tru64 UNIX domain socket /dev/log file, which is automatically
created by the syslogd daemon
• An Internet domain socket, which is specified in the /etc/services
file
• The special file /dev/klog, which logs only kernel messages
Messages from other programs use the openlog, syslog, and closelog
calls.
When the syslogd daemon is started, it creates the
/var/run/syslog.pid file, where the syslogd daemon stores its process
identification number. Use the process identification number to stop the
syslogd daemon before you shut down the system.
During normal system operation, the syslogd daemon is called if data is
put in the kernel syslog message buffer, located in physical memory. The
syslogd daemon reads the /dev/klog file and gets a copy of the kernel
syslog message buffer. The syslogd daemon starts at the beginning of the
buffer and sequentially processes each message that it finds. Each message
is prefixed by facility and priority codes, which are the same as those
13–10 Administering Events and Errors