xref: /netbsd-src/usr.sbin/syslogd/syslogd.8 (revision 001c68bd94f75ce9270b69227c4199fbf34ee396)
1.\"	$NetBSD: syslogd.8,v 1.31 2003/05/14 12:15:01 wiz Exp $
2.\"
3.\" Copyright (c) 1983, 1986, 1991, 1993
4.\"	The Regents of the University of California.  All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. All advertising materials mentioning features or use of this software
15.\"    must display the following acknowledgement:
16.\"	This product includes software developed by the University of
17.\"	California, Berkeley and its contributors.
18.\" 4. Neither the name of the University nor the names of its contributors
19.\"    may be used to endorse or promote products derived from this software
20.\"    without specific prior written permission.
21.\"
22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32.\" SUCH DAMAGE.
33.\"
34.\"     from: @(#)syslogd.8	8.1 (Berkeley) 6/6/93
35.\"
36.Dd May 25, 2002
37.Dt SYSLOGD 8
38.Os
39.Sh NAME
40.Nm syslogd
41.Nd log systems messages
42.Sh SYNOPSIS
43.Nm
44.Op Fl dns
45.Bk -words
46.Op Fl f Ar config_file
47.Ek
48.Bk -words
49.Op Fl g Ar group
50.Ek
51.Bk -words
52.Op Fl m Ar mark_interval
53.Ek
54.Bk -words
55.Op Fl P Ar file_list
56.Ek
57.Bk -words
58.Oo
59.Fl p Ar log_socket
60.Op Fl p Ar log_socket2 ...
61.Oc
62.Ek
63.Bk -words
64.Op Fl t Ar chroot_dir
65.Ek
66.Bk -words
67.Op Fl u Ar user
68.Ek
69.Sh DESCRIPTION
70.Nm
71reads and logs messages to the system console, log files, other
72machines and/or users as specified by its configuration file.
73The options are as follows:
74.Bl -tag -width 15n
75.It Fl d
76Enable debugging to the standard output,
77and do not disassociate from the controlling terminal.
78.It Fl f
79Specify the pathname of an alternative configuration file;
80the default is
81.Pa /etc/syslog.conf .
82.It Fl g Ar group
83Set GID to
84.Ar group
85after the sockets and log files have been opened.
86.It Fl m
87Select the number of minutes between ``mark'' messages;
88the default is 20 minutes.
89.It Fl n
90Do not perform hostname lookups; report only numeric addresses.
91.It Fl P
92Specify the pathname of a file containing a list of sockets to be
93created.
94The format of the file is simply one socket per line.
95.It Fl p
96Specify the pathname of a log socket.
97Multiple
98.Fl p
99options create multiple log sockets.
100If no
101.Fl p
102arguments are created, the default socket of
103.Pa /var/run/log
104is used.
105.It Fl s
106Select
107.Dq secure
108mode, in which
109.Nm
110does not listen on a UDP socket but only communicates over a
111.Ux
112domain socket.
113This is valuable when the machine on
114which
115.Nm
116runs is subject to attack over the network and it is desired
117that the machine be protected from attempts to remotely fill logs
118and similar attacks.
119.It Fl t Ar chroot_dir
120.Xr chroot 2
121to
122.Ar chroot_dir
123after the sockets and log files have been opened.
124.It Fl u Ar user
125Set UID to
126.Ar user
127after the sockets and log files have been opened.
128.El
129.Pp
130.Nm
131reads its configuration file when it starts up and whenever it
132receives a hangup signal.
133For information on the format of the configuration file,
134see
135.Xr syslog.conf 5 .
136.Pp
137.Nm
138reads messages from the
139.Ux
140domain socket
141.Pa /var/run/log ,
142from an Internet domain socket specified in
143.Pa /etc/services ,
144and from the special device
145.Pa /dev/klog
146(to read kernel messages).
147.Pp
148.Nm
149creates the file
150.Pa /var/run/syslogd.pid ,
151and stores its process
152id there.
153This can be used to kill or reconfigure
154.Nm .
155.Pp
156By using multiple
157.Fl p
158options, one can set up many chroot environments by passing the pathname
159to the log socket
160.Pa ( /var/run/log )
161in each chroot area to
162.Nm .
163For example:
164.Dl syslogd -p /var/run/log -p /web/var/run/log -p /ftp/var/run/log
165.Pp
166Note: the normal log socket must now also be passed to
167.Nm .
168.Pp
169The logged message includes the date, time, and hostname (or pathname of
170the log socket).
171Commonly, the program name and the process id is included.
172.Pp
173Accesses from UDP socket can be filtered by libwrap configuration files, like
174.Pa /etc/hosts.deny .
175Specify
176.Dq Li syslogd
177in
178.Ar daemon_list
179portion of the configuration files.
180Refer to
181.Xr hosts_access 5
182for details.
183.Ss SYSLOG PROTOCOL NOTES
184The message sent to
185.Nm
186should consist of a single line.
187The message can contain a priority code, which should be a preceding
188decimal number in angle braces, for example,
189.Sq Aq 5 .
190This priority code should map into the priorities defined in the
191include file
192.Aq Pa sys/syslog.h .
193.Sh FILES
194.Bl -tag -width /var/run/syslogd.pid -compact
195.It Pa /etc/syslog.conf
196The configuration file.
197.It Pa /var/run/syslogd.pid
198The process id of current
199.Nm .
200.It Pa /var/run/log
201Name of the
202.Ux
203domain datagram log socket.
204.It Pa /dev/klog
205The kernel log device.
206.El
207.Sh SEE ALSO
208.Xr logger 1 ,
209.Xr syslog 3 ,
210.Xr services 5 ,
211.Xr syslog.conf 5 ,
212.Xr newsyslog 8
213.Sh HISTORY
214The
215.Nm
216command appeared in
217.Bx 4.3 .
218Support for multiple log sockets appeared in
219.Nx 1.4 .
220libwrap support appeared in
221.Nx 1.6 .
222