Technical data

4. Packages

If you have a so-called “log host” in your network you can redirect the Syslog messages

to that host if you supply its IP address.

Beispiel:

SYSLOGD_DEST_1='*.* @192.168.4.1'

The “@” sign has to be prepended to the IP address.

If you want the Syslog messages to be delivered to multiple destinations it is necessary

to increase the variable SYSLOGD_DEST_N (number of destinations used) accordingly and

to ﬁll the variables SYSLOG_DEST_1, SYSLOG_DEST_2 etc. with appropriate content.

The syntax ‘*.*’ directs syslogd to log all messages. However, you are also able to

constrain the messages to be logged for certain destinations by the use of so-called “pri-

orities”. In this case you need to replace the asterisk (*) after the dot (.) by one of the

following keywords:

• debug

• info

• notice

• warning (deprecated: warn)

• err (deprecated: error)

• crit

• alert

• emerg (deprecated: panic)

The items in the list are descending sorted according to severity. The keywords “error”,

“warn”, and “panic” are deprecated—you should not use them anymore.

You can replace the asterisk (*) in front of the dot by a so-called “facility”. However, a

detailed explanation is outside this scope. You can ﬁnd an overview over the available

facilities at the man page of syslog.conf:

http://linux.die.net/man/5/syslog.conf

In most cases an asterisk is completely suﬃcient. Example:

SYSLOGD_DEST_1='*.warning @192.168.4.1'

Windows hosts can serve as log hosts as well as Unix/Linux hosts. You can ﬁnd links to

adequate software at http://www.fli4l.de/en/other/links/. Using a log host is strongly

recommended if you want a detailed logging protocol. The protocol is also useful for

debugging purposes. The Windows client imonc also “understands” the Syslog protocol

and is able to display the messages in a window.

Unfortunately, messages generated during the boot process cannot be directed to syslogd.

However, you can conﬁgure ﬂi4l to use a serial port as a terminal. You can ﬁnd more

information on this topic in the section Console settings (Page 29).

SYSLOGD_ROTATE You can use SYSLOGD_ROTATE in order to control whether Syslog message

ﬁles are rotated once a day, thereby archiving the messages of the last x days.