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: syslogd.8,v 1.8 1997/02/22 16:14:00 peter Exp $
|
33.\" $Id: syslogd.8,v 1.9 1997/04/26 00:00:32 pst Exp $ |
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
|
42.Nm |
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
|
48The 49.Nm 50daemon reads and logs messages to the system console, log files, other |
51machines and/or users as specified by its configuration file. 52The options are as follows: 53.Bl -tag -width Ds 54.It Fl d 55Put
|
55.Nm syslogd
|
56.Nm |
57into debugging mode. This is probably only of use to developers working on
|
57.Nm syslogd .
|
58.Nm Ns . |
59.It Fl f 60Specify the pathname of an alternate configuration file; 61the default is 62.Pa /etc/syslog.conf . 63.It Fl s 64Operate in secure mode. Do not listen for log message from remote machines. 65.It Fl m
|
65Select the number of minutes between ``mark'' messages;
66the default is 20 minutes.
|
66Select the number of minutes between 67.Dq mark 68messages; the default is 20 minutes. |
69.It Fl p 70Specify the pathname of an alternate log socket; 71the default is 72.Pa /var/run/log . 73.El 74.Pp
|
73.Nm Syslogd
74reads its configuration file when it starts up and whenever it
|
75The 76.Nm 77daemon reads its configuration file when it starts up and whenever it |
78receives a hangup signal. 79For information on the format of the configuration file, 80see 81.Xr syslog.conf 5 . 82.Pp
|
80.Nm Syslogd
81reads messages from the
|
83The 84.Nm 85daemon reads messages from the |
86.Tn UNIX 87domain socket 88.Pa /var/run/log , 89from an Internet domain socket specified in 90.Pa /etc/services , 91and from the special device 92.Pa /dev/klog 93(to read kernel messages). 94.Pp
|
91.Nm Syslogd
92creates the file
|
95The 96.Nm 97daemon creates the file |
98.Pa /var/run/syslog.pid , 99and stores its process 100id there. 101This can be used to kill or reconfigure
|
97.Nm syslogd .
|
102.Nm Ns . |
103.Pp 104The message sent to
|
100.Nm syslogd
|
105.Nm |
106should consist of a single line. 107The message can contain a priority code, which should be a preceding 108decimal number in angle braces, for example, 109.Sq Aq 5. 110This priority code should map into the priorities defined in the 111include file 112.Aq Pa sys/syslog.h . 113.Sh FILES 114.Bl -tag -width /var/run/syslog.pid -compact 115.It Pa /etc/syslog.conf 116The configuration file. 117.It Pa /var/run/syslog.pid 118The process id of current
|
114.Nm syslogd .
|
119.Nm Ns . |
120.It Pa /var/run/log 121Name of the 122.Tn UNIX 123domain datagram log socket. 124.It Pa /dev/klog 125The kernel log device. 126.El 127.Sh SEE ALSO 128.Xr logger 1 , 129.Xr syslog 3 , 130.Xr services 5 , 131.Xr syslog.conf 5 132.Sh HISTORY 133The 134.Nm 135command appeared in 136.Bx 4.3 . 137.Sh BUGS 138The ability to log messages received in UDP packets is equivalent to 139an unauthenticated remote disk-filling service, and should probably be 140disabled by default. Some sort of 141.No inter- Ns Nm syslogd 142authentication mechanism ought to be worked out. 143.Pp 144The log socket was moved from 145.Pa /dev 146to ease the use of a read-only root filesystem. This may confuse 147some old binaries so that a symbolic link might be used for a 148transitional period.
|