Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
SYSLOGD(8)		FreeBSD	System Manager's Manual		    SYSLOGD(8)

     modular syslog daemon -- log systems messages

     syslogd [-c] [-u] [-n] [-A] [-d level] [-f	config_file]
	     [-m mark_interval]	[-a path] [-p log_socket] [-i input]
	     [-P pidfile]

     Modular syslog daemon reads and logs messages to the system console, log
     files, other machines and/or users	as specified by	its configuration
     file. This	implementation was based on OpenBSD's syslog daemon.

     Supported command line options are:

     -d	level
	     Enable debugging to the standard output, and do not disassociate
	     from the controlling terminal. The	level is a number used to dif-
	     ferentiate	error reports. Up to 10	reports	all critical errors
	     that stop the daemon from working;	up to 20 are the serious er-
	     rors that stop some input or output; up to	30 are noncritical er-
	     rors; up to 100 are warnings and potential	errors;	up to 200 are
	     informative messages; and finally up to 250 are all possible re-
	     porting on	what is	going on.

     -f	config_file
	     Specify the pathname of an	alternate configuration	file; the de-
	     fault is /usr/local/etc/syslog.conf.

     -m	mark_interval
	     Select the	number of minutes between ``mark'' messages; the de-
	     fault is 20 minutes.

     -u	     Allow the historical ``insecure'' mode, in	which syslogd will ac-
	     cept input	from the UDP port as specified in /etc/services.  Some
	     software wants this, but you can be subjected to a	variety	of at-
	     tacks over	the network, including attackers remotely filling

     -P	pidfile
	     Specify an	alternate pidfile.

     -p	log_socket
	     Specify the pathname of an	alternate log socket to	be used	in-
	     stead; the	default	is /var/run/log.  This option is deprecated by
	     -i	option.

     -a	path
	     Specify a location	where syslogd should place an additional log
	     socket.  The primary use for this is to place additional log
	     sockets in	/var/run/log of	various	chroot filespaces. This	option
	     is	predecated by -i option.

     -i	input_module [module_arguments]
	     Enables the specified input modules, see im_*(8).

     -n	     Disables opening default inputs when there	aren't given on	com-
	     mand line.

     -c	     Disables opening console device, useful for non root testing.

     -A	     Use local host name with it's domain.

     Syslogd reads its configuration file when it starts up and	whenever it
     receives a	hangup signal.	For information	on the format of the configu-
     ration file, see syslog.conf(5).

     Syslogd creates the file /var/run/, and stores its process id
     there.  This can be used to kill or reconfigure syslogd.

     The message sent to syslogd 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, `<5>'.  This	priority code should map into
     the priorities defined in the include file	<sys/syslog.h>.

     To	run modular syslog on BSD systems you should:

	   # syslogd

     with the command above two	inputs modules are created, bsd, that reads
     BSD kernel	messages from /dev/klog, and unix, opens /var/run/log socket
     to	log standard messages.	To run modular syslog on Linux systems you

	   # syslogd

     with the command above two	inputs modules are created, linux, that	reads
     linux kernel messages from	/dev/klog, and unix, opens /var/run/log	socket
     to	log standard messages.

			  The configuration file.
     /var/run/  The process id of current syslogd.
     /var/run/log	  Name of the UNIX domain datagram log socket.
     /dev/klog		  The kernel log device.

     syslog(3),	syslog.conf(5),	im_bsd(8), im_doors(8),	im_linux(8),
     im_streams(8), im_tcp(8), im_unix(8), im_udp(8), om_classic(8),
     om_mysql(8), om_peo(8), om_pgsql(8), om_regex(8), om_tcp(8), om_udp(8),
     peochk(8),	syslogd(8)

     Modular syslog is based on	the original syslogd daemon appeared in

     Submit bugs at this project's Sourceforge Bug reporting system at: You
     may also report them directly to the authors; send	an email to, describing the problem the most you can, containing
     also machine description, hardware	description, the configuration file
     (/usr/local/etc/syslog.conf), the OS description, and the invoking	com-
     mand line.	 The more you describe the bug,	the faster we can fix it.

Core-SDI			 June 6, 1993			      Core-SDI


Want to link to this manual page? Use this URL:

home | help