Sysklogd provides two system utilities which provide support for system logging and kernel message trapping. Support of both Internet and unix domain sockets enables this utility package to support both local and remote logging.

System logging is provided by a version of syslogd derived from BSD. Support for kernel logging is provided by the klogd utility that allows kernel logging to be conducted in either a standalone fashion or as a client of syslogd.

syslogd provides a kind of logging that many modern programs use. Every logged message contains at least a time and a hostname field, and normally a program name field, but it depends on the logging program.

The main configuration file /etc/syslog.conf or an alternative file, given with the -f option, is read at startup. Any lines that begin with the hash mark ("#") and empty lines are ignored. If an error occurs during parsing a line, the whole line is ignored.

>syslogd [ -a socket ] [ -d ] [ -f config-file ] [ -h ] [ -l hostlist ] 
        [ -m interval ] [ -n ] [ -p socket ] [-r ] [ -s domainlist ] 
        [ -u user ] [ -v ]

Options

Signals

Syslogd reacts to a set of signals. You may easily send a signal to syslogd using the following:

kill -SIGNAL `cat /var/run/syslogd.pid`

where SIGNAL is one of the following signals:

Syslogd uses a slightly different syntax for its configuration file than the original BSD sources. Originally all messages of a specific priority and above were forwarded to the log file.

For example, the following line caused ALL output from daemons using the daemon facilities (debug is the lowest priority, so everything higher will also match) to go into /usr/adm/daemons:

# Sample syslog.conf 
daemon.debug 		/usr/adm/daemons

Under the new scheme this behavior remains the same. The difference is the addition of four new specifiers, the asterisk (*) wildcard, the equal sign (=), the exclamation mark (!), and the minus sign (-).

The * specifies that all messages for the specified facility are to be directed to the destination. Note that this behavior is degenerate with specifying a priority level of debug. Users have indicated that the asterisk notation is more intuitive.

The = wildcard is used to restrict logging to the specified priority class. This allows, for example, routing only debug messages to a particular logging source.

For example, the following line in syslog.conf would direct debug messages from all sources to the /usr/adm/debug file.

# Sample syslog.conf 
*.=debug 		/usr/adm/debug

The ! is used to exclude logging of the specified priorities. This affects all (!) possibilities of specifying priorities.

For example, the following lines would log all messages of the facility mail except those with the priority info to the /usr/adm/mail file. And all messages from news.info (including) to news.crit (excluding) would be logged to the /usr/adm/news file.

# Sample syslog.conf 
mail.*;mail.!=info 	/usr/adm/mail 
news.info;news.!crit 	/usr/adm/news

You may use it intuitively as an exception specifier. The above mentioned interpretation is inverted. Doing that you may use

mail.none

or

mail.!*

or

mail.!debug

to skip every message that comes with a mail facility.

The "-" may only be used to prefix a file name if you want to omit sync'ing the file after every write to it.

To enable remote logging, specify the -r option on the command line. The default behavior is that syslogd won't listen to the network.

The strategy is to have syslogd listen on a unix domain socket for locally generated log messages. This behavior will allow syslogd to interoperate with the syslog found in the standard C library. At the same time syslogd listens on the standard syslog port for messages forwarded from other hosts. To have this work correctly the services files (typically found in /etc) must have the following entry:

syslog 514/udp

If this entry is missing syslogd neither can receive remote messages nor send them, because the UDP port can't be opened. Instead syslogd will die immediately, and print an error message.

To cause messages to be forwarded to another host replace the normal file line in the syslog.conf file with the name of the host to which the messages is to be sent prepended with an @.

For example, to forward ALL messages to a remote host use the following syslog.conf entry:

# Sample syslogd configuration file to 
# messages to a remote host forward all. 
*.* 		@hostname

To forward all kernel messages to a remote host the configuration file would be as follows:

# Sample configuration file to forward all kernel 
# messages to a remote host. 
kern.* 		@hostname

If the remote hostname cannot be resolved at startup, because the name server might not be accessible (it may be started after syslogd) syslogd will retry to resolve the name ten times and then complain. Another possibility to avoid this is to place the hostname in /etc/hosts.

To avoid this, no messages received from a remote host are sent out to another (or the same) remote host anymore. If you experience are setup in which you need this behavior, please use the -h command line switch. However, this option needs to be handled with caution since a syslog loop can fill up hard disks quite fast.

If the remote host is located in the same domain as the host, syslogd is running on, only the simple hostname will be logged instead of the whole fqdn.

In a local network you may provide a central log server to have all the important information kept on one machine. If the network consists of different domains you don't have to complain about logging fully qualified names instead of simple hostnames. You may want to use the strip-domain feature -s of this server. You can tell the syslogd to strip off several domains other than the one the server is located in and only log simple hostnames.

Using the -l option there's also a possibility to define single hosts as local machines. This, too, results in logging only their simple hostnames and not the fqdns.

The UDP socket used to forward messages to remote hosts or to receive messages from them is only opened when it is needed. In releases prior to 1.3-23 it was opened every time but not opened for reading or forwarding respectively.

When debugging is turned on using -d option, syslogd will be very verbose by writing much of what it does to stdout. Whenever the configuration file is reread and re-parsed you'll see a tabular, corresponding to the internal data structure. This tabular consists of four fields:

Security Notes

There is the potential for the syslogd daemon to be used as a conduit for a denial of service attack. A rogue program (or programmer) could very easily flood the syslogd daemon with syslog messages resulting in the log files consuming all the remaining space on the filesystem. Activating logging over the inet domain sockets will of course expose a system to risks outside of programs or individuals on the local machine.

There are a number of methods of protecting a machine:

• Implement kernel firewalling to limit which hosts or networks have access to the 514/UDP socket. 
•  Logging can be directed to an isolated or non-root filesystem which, if filled, will not impair themachine. 
•  The ext2 filesystem can be used which can be configured to limit a certain percentage of a filesystem to usage by root only. Note that this will require syslogd to be run as a non-root process, and prevent usage of remote logging since syslogd will be unable to bind to the 514/UDP socket. 
•  Disabling inet domain sockets will limit risk to the local machine.