Installation guide

specified in the /etc/syslog.conf file. The syslogd daemon then sends
the messages to the destinations specified in the file.
To stop the syslogd event-logging daemon, use the following command:
# kill ‘cat /var/run/syslog.pid‘
You can apply changes that you make to the /etc/syslog.conf
configuration file without shutting down the system by using the following
command:
# kill -HUP ‘cat /var/run/syslog.pid‘
13.2.3.2 The binlogd Daemon
You must ensure that the init program starts the binlogd daemon. If the
binlogd daemon does not start, or if you want to specify options with the
command that starts the binlogd daemon, you must edit the
/sbin/init.d/syslog file and either include or modify the binlogd
command line. Note that you can also invoke the command manually.
The command that starts the binlogd daemon has the following syntax:
/usr/sbin/binlogd
[-d][-f config_file]
Refer to the binlogd(8) reference page for information on command
options.
The binlogd daemon reads binary event records from the following:
• An Internet domain socket (binlogd, 706/udp), which is specified in
the /etc/services file
• The /dev/kbinlog special file
When the binlogd daemon starts, it creates the /var/run/binlogd.pid
file, where the binlogd daemon stores its process identification number.
Use the process identification number to stop or reconfigure the binlogd
daemon.
During normal system operation, the binlogd daemon is called if data is
put into the kernel’s binary event-log buffer or if data is received on the
Internet domain socket. The binlogd daemon then reads the data from
the /dev/kbinlog special file or from the socket. Each record contains an
event class code and a severity level code. The binlogd daemon processes
each binary event record and logs it to the destination specified in the
/etc/binlog.conf file.
To stop the binlogd daemon, use the following command:
# kill ‘cat /var/run/binlogd.pid‘
Administering Events and Errors 13–11