Configuring the syslogd messaging facility
Through the syslogd messaging facility, you can send event messages to a finite list of facilities.
To configure the syslogd to write all user-friendly facility messages to a specific log file, add this line to the /etc/syslogd.conf file:
|SafeLinx Server log level||Syslogd priorities||Description|
|error||err||Messages about unexpected events on which you must take action|
|warn||warning||Messages about events on which you may or may not need to take action|
|log||info||General information messages|
|trcart||info||Hexadecimal dump of data packets|
|trcip||info||Hexadecimal dump of only IP-related data packets|
|status||info||Dump of status information, such as packet rates, byte rates, and system load|
|tcp-lite||info||Messages about data using the TCP-Lite transport|
|debug||debug||Data used for problem analysis|
The following examples make use of priority to log messages to different files.
When changes are made to the syslog.conf file, the syslogd must be refreshed or restarted. On AIX, this command is:
refresh - s syslogd
Before you refresh or restart the syslogd daemon, make sure that the files that you are using to log messages exist on the file system.
There are several other options for configuring options such as the maximum log file sizes, time/date format, or sending logs to a remote server. Consult your operating system documentation for this specific information.