gtpc1m4zTransmission Control Protocol/Internet Protocol

Operating the Syslog Daemon

Use the ZINET and ZFILE commands to operate and maintain the syslog daemon.

Starting the Syslog Daemon

If you specify AUTO for the ACTIVATION parameter when adding the syslog daemon to the IDCF, the syslog daemon will start automatically when the Internet daemon is started. If you specify OPER for the ACTIVATION parameter, you must start the syslog daemon manually. To start the syslog daemon manually, enter the following from the BSS:

ZINET START S-SYSLOGD

When the syslog daemon is defined to start automatically, if there is no TCP/IP transport active when the syslog daemon starts or if TCP/IP is recycled, the syslog daemon will not establish or re-establish communication with TCP/IP when it becomes available. If this occurs, you can use the syslog daemon only for local applications.

Stopping the Syslog Daemon

To stop the syslog daemon, enter the following from the BSS:

ZINET STOP S-SYSLOGD

To force the syslog daemon to read its configuration file again and activate any modified parameters without stopping, enter the following to send a SIGHUP signal:

ZFILE kill -s SIGHUP $(cat /etc/syslog.pid)

The syslog daemon will continue to append log messages to the files you specify in the /etc/syslog.conf file.

Messages are read from the FIFO special file and the Internet domain datagram socket.

Offloading Log Files

To periodically offload log files to another location and delete unwanted messages without stopping the syslog daemon, do the following:

  1. Create two syslog daemon configuration files called /etc/syslog.conf.a and /etc/syslog.conf.b. These two files will be identical except that all log files end with either a or b.
  2. If your current /etc/syslog.conf file was created from your syslog.conf.a file, enter the ZFILE cp command to copy your syslog.conf.b file to the /etc/syslog.conf file.
  3. Enter ZFILE kill -s SIGHUP $(cat /etc/syslog.pid) to send a SIGHUP signal to the syslog daemon. This stops the syslog daemon from writing to the a log files and forces it to write to the b log files.
  4. Offload the a files using TFTP or FTP and delete their current contents.