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