.\" syslog.conf - syslogd(8) configuration file
-.\" Copyright (c) 1995,2006 Joey Schulze <joey@infodrom.org>
+.\" Copyright (c) 1995-2007 Martin Schulze <joey@infodrom.org>
.\"
.\" This file is part of the sysklogd package, a kernel and system log daemon.
.\"
is able to understand an extended syntax. One rule can be divided
into several lines if the leading line is terminated with an backslash
(``\\'').
-
.SH SELECTORS
The selector field itself again consists of two parts, a
.I facility
.BR warning "), " err ", " error " (same as " err "), " crit ", "
.BR alert ", " emerg ", " panic " (same as " emerg ).
The keywords
-.BR error ", " warn " and " panic
+.BR warn ", " error " and " panic
are deprecated and should not be used anymore. The
.I priority
defines the severity of the message
using the semicolon (``;'') separator. Please note that each selector in
the
.I selector
-field is capable to overwrite the preceding ones. Using this
+field is capable of overwriting the preceding ones. Using this
behavior you can exclude some priorities from the pattern.
This
to ignore only this single priority. If you use both extensions
than the exclamation mark must occur before the equation sign, just
use it intuitively.
-
.SH ACTIONS
The action field of a rule describes the abstract term
``logfile''. A ``logfile'' need not to be a real file, btw. The
.SS List of Users
Usually critical messages are also directed to ``root'' on that
machine. You can specify a list of users that shall get the message by
-simply writing the login. You may specify more than one user by
-separating them with commas (``,''). If they're logged in they
-get the message. Don't think a mail would be sent, that might be too
-late.
+simply writing the username. You may specify more than one user by
+separating the usernames with commas (``,''). If they're logged in they
+will receive the log messages.
.SS Everyone logged on
Emergency messages often go to all users currently online to notify
this
.IR wall (1)-feature
use an asterisk (``*'').
-
.SH EXAMPLES
Here are some example, partially taken from a real existing site and
-configuration. Hopefully they rub out all questions to the
+configuration. Hopefully they rub out all questions on the
configuration, if not, drop me (Joey) a line.
.IP
.nf
.IP
.nf
-# The tcp wrapper loggs with mail.info, we display
+# The tcp wrapper logs with mail.info, we display
# all the connections on tty12
#
mail.=info /dev/tty12
.IR /dev/tty12 ,
the 12th console. For example the tcpwrapper
.BR tcpd (8)
-uses this as it's default.
+uses this as its default.
.IP
.nf
This rule would redirect all messages to a remote host called
finlandia. This is useful especially in a cluster of machines where
all syslog messages will be stored on only one machine.
-
.SH CONFIGURATION FILE SYNTAX DIFFERENCES
.B Syslogd
uses a slightly different syntax for its configuration file than
.I /etc/syslog.conf
Configuration file for
.B syslogd
-
.SH BUGS
The effects of multiple selectors are sometimes not intuitive. For
example ``mail.crit,*.err'' will select ``mail'' facility messages at
the level of ``err'' or higher, not at the level of ``crit'' or
higher.
-
.SH SEE ALSO
.BR sysklogd (8),
.BR klogd (8),
.BR logger (1),
.BR syslog (2),
-.BR syslog (3)
-
+.BR syslog (3).
.SH AUTHORS
The
.B syslogd
-is taken from BSD sources, Greg Wettstein (greg@wind.enjellic.com)
-performed the port to Linux, Martin Schulze (joey@linux.de)
-made some bugfixes and added some new features.
+is taken from BSD sources, Greg Wettstein <greg@wind.enjellic.com>
+performed the port to Linux, Martin Schulze <joey@infodrom.org>
+fixed some bugs, added several new features and took over maintenance.