Setting up syslogd

The TCP/IP documentation recommends writing Policy Agent messages to the z/OS® UNIX syslog instead of using the default log file. AT-TLS always writes messages to the z/OS UNIX syslog.

In order to do so, the z/OS UNIX syslog daemon, syslogd, must be configured and active. You also need a mechanism to control the size of the log files created by syslogd.

The following sample configuration file updates can be used to configure and start syslogd, with a simple log file management mechanism (erase existing logs when z/OS UNIX starts and create new ones upon syslogd startup).
  • /etc/services
    syslog          514/udp
  • /etc/syslog.conf
    # /etc/syslog.conf - control output of syslogd
# 1. all files with will be printed to /tmp/syslog.auth.log
auth.*           /tmp/syslog.auth.log
# 2. all error messages printed to /tmp/syslog.error.log
*.err            /tmp/syslog.error.log
# 3. all debug and above messages printed to /tmp/syslog.debug.log
*.debug          /tmp/syslog.debug.log
# The files named must exist before the syslog daemon is started,
# unless -c startup option is used
  • /etc/rc
    # Start the SYSLOGD daemon for logging
# (clean up old logs)
sed -n '/^#/!s/.* \(.*\)/\1/p' /etc/syslog.conf | xargs -i rm {}
# (create new logs and add userid of message sender)
_BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -cuf /etc/syslog.conf &
sleep 5