reads and logs messages to the system console, log files, other
machines and/or users as specified by its configuration file.
The options are as follows:
Print version number and exit.
Display help information and exit.
Enter debug mode. syslogd does not put itself in the background, does
not fork and shows debug information.
Specify additional sockets from that syslogd has to listen to.
This is needed if you are going to let some daemon run within
a chroot()'ed environment. You can specify up to 19 additional
sockets.
Specify the pathname of an alternate configuration file;
the default is system specific and displayed in the help output.
Enable forwarding remote messages. By default syslogd will not
forward messages it receives from remote hosts.
A colon-seperated lists of hosts which should be considered local;
they are logged by their hostnames instead by their FQDN.
Select the number of minutes between ``mark'' messages;
the default is 20 minutes. Setting it to 0 disables timestamps.
Suppress backgrounding and detachment of the daemon from its
controlling terminal.
Specify the pathname of an alternate log socket.
The default is systemspecific and displayed in the help output.
Enable to receive remote messages using an internet domain socket.
The default is to not receive any messages from the network. Older
version always accepted remote messages.
A colon-seperated list of domainnames which should be stripped from
the FQDNs of hosts when logging.
Do not listen to the kernel log device. This is only supported on
systems which define a kernel log device, on all others this is already
the default, and the option will be silently ignored.
Do not listen to any unix domain socket. This option overrides -p and -a.
Do not forward any messages. This overrides -h.
reads its configuration file when it starts up and whenever it
receives a hangup signal.
For information on the format of the configuration file,
see
reads messages from the
domain socket
from an Internet domain socket specified in
and from the special device
(to read kernel messages).
creates the file
and stores its process
id there.
This can be used to kill or reconfigure
The message sent to
should consist of a single line.
The message can contain a priority code, which should be a preceding
decimal number in angle braces, for example,
This priority code should map into the priorities defined in the
include file
The configuration file.
The process id of current
Name of the
domain datagram log socket.
The kernel log device.
The
command appeared in