1.\" Copyright (c) 1983, 1986, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by the University of 15.\" California, Berkeley and its contributors. 16.\" 4. Neither the name of the University nor the names of its contributors 17.\" may be used to endorse or promote products derived from this software 18.\" without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)syslogd.8 8.1 (Berkeley) 6/6/93 33.\" $Id$ 34.\" 35.Dd October 12, 1995 36.Dt SYSLOGD 8 37.Os BSD 4.2 38.Sh NAME 39.Nm syslogd 40.Nd log systems messages 41.Sh SYNOPSIS 42.Nm syslogd 43.Op Fl dI 44.Op Fl f Ar config_file 45.Op Fl m Ar mark_interval 46.Op Fl p Ar log_socket 47.Sh DESCRIPTION 48.Nm Syslogd 49reads and logs messages to the system console, log files, other 50machines and/or users as specified by its configuration file. 51The options are as follows: 52.Bl -tag -width Ds 53.It Fl d 54Put 55.Nm syslogd 56into debugging mode. This is probably only of use to developers working on 57.Nm syslogd . 58.It Fl f 59Specify the pathname of an alternate configuration file; 60the default is 61.Pa /etc/syslog.conf . 62.It Fl I 63Do not log messages received in UDP packets. 64.It Fl m 65Select the number of minutes between ``mark'' messages; 66the default is 20 minutes. 67.It Fl p 68Specify the pathname of an alternate log socket; 69the default is 70.Pa /dev/log . 71.El 72.Pp 73.Nm Syslogd 74reads its configuration file when it starts up and whenever it 75receives a hangup signal. 76For information on the format of the configuration file, 77see 78.Xr syslog.conf 5 . 79.Pp 80.Nm Syslogd 81reads messages from the 82.Tn UNIX 83domain socket 84.Pa /dev/log , 85from an Internet domain socket specified in 86.Pa /etc/services , 87and from the special device 88.Pa /dev/klog 89(to read kernel messages). 90.Pp 91.Nm Syslogd 92creates the file 93.Pa /var/run/syslog.pid , 94and stores its process 95id there. 96This can be used to kill or reconfigure 97.Nm syslogd . 98.Pp 99The message sent to 100.Nm syslogd 101should consist of a single line. 102The message can contain a priority code, which should be a preceding 103decimal number in angle braces, for example, 104.Sq Aq 5. 105This priority code should map into the priorities defined in the 106include file 107.Aq Pa sys/syslog.h . 108.Sh FILES 109.Bl -tag -width /var/run/syslog.pid -compact 110.It Pa /etc/syslog.conf 111The configuration file. 112.It Pa /var/run/syslog.pid 113The process id of current 114.Nm syslogd . 115.It Pa /dev/log 116Name of the 117.Tn UNIX 118domain datagram log socket. 119.It Pa /dev/klog 120The kernel log device. 121.El 122.Sh SEE ALSO 123.Xr logger 1 , 124.Xr syslog 3 , 125.Xr services 5 , 126.Xr syslog.conf 5 127.Sh HISTORY 128The 129.Nm 130command appeared in 131.Bx 4.3 . 132.Sh BUGS 133The ability to log messages received in UDP packets is equivalent to 134an unauthenticated remote disk-filling service, and should probably be 135disabled by default. Some sort of 136.No inter- Ns Nm syslogd 137authentication mechanism ought to be worked out. 138 139