|
|
1.1 root 1: .\" Copyright (c) 1983, 1986 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted provided
5: .\" that: (1) source distributions retain this entire copyright notice and
6: .\" comment, and (2) distributions including binaries display the following
7: .\" acknowledgement: ``This product includes software developed by the
8: .\" University of California, Berkeley and its contributors'' in the
9: .\" documentation or other materials provided with the distribution and in
10: .\" all advertising materials mentioning features or use of this software.
11: .\" Neither the name of the University nor the names of its contributors may
12: .\" be used to endorse or promote products derived from this software without
13: .\" specific prior written permission.
14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
17: .\"
18: .\" @(#)syslogd.8 6.8 (Berkeley) 6/27/90
19: .\"
20: .TH SYSLOGD 8 "June 27, 1990"
21: .UC 5
22: .SH NAME
23: syslogd \- log systems messages
24: .SH SYNOPSIS
25: .B syslogd
26: [
27: .BI \-f configfile
28: ] [
29: .BI \-m markinterval
30: ] [
31: .B \-d
32: ]
33: .SH DESCRIPTION
34: .I Syslogd
35: reads and logs messages into a set of files
36: described by the configuration file
37: /etc/syslog.conf.
38: Each message is one line.
39: A message can contain a priority code,
40: marked by a number in angle braces
41: at the beginning of the line.
42: Priorities are defined in
43: .RI < sys/syslog.h >.
44: .I Syslogd
45: reads from the UNIX domain socket
46: .IR /dev/log ,
47: from an Internet domain socket specified in
48: .IR /etc/services ,
49: and from the special device
50: .I /dev/klog
51: (to read kernel messages).
52: .PP
53: .I Syslogd
54: configures when it starts up
55: and whenever it receives a hangup signal.
56: Lines in the configuration file have a
57: .I selector
58: to determine the message priorities to which the line applies
59: and an
60: .IR action .
61: The
62: .I action
63: field are separated from the selector by one or more tabs.
64: .PP
65: Selectors are semicolon separated lists of priority specifiers.
66: Each priority has a
67: .I facility
68: describing the part of the system that generated the message,
69: a dot,
70: and a
71: .I level
72: indicating the severity of the message.
73: Symbolic names may be used.
74: An asterisk selects all facilities.
75: All messages of the specified level or higher (greater severity)
76: are selected.
77: More than one facility may be selected using commas to separate them.
78: For example:
79: .PP
80: .ti +5
81: *.emerg;mail,daemon.crit
82: .PP
83: Selects all facilities at the
84: .I emerg
85: level and the
86: .I mail
87: and
88: .I daemon
89: facilities at the
90: .I crit
91: level.
92: .PP
93: Known facilities and levels
94: recognized by
95: .I syslogd
96: are those listed in
97: .IR syslog (3)
98: without the leading ``LOG_''.
99: The additional facility
100: ``mark'' has a message at priority LOG_INFO sent to it every
101: 20 minutes
102: (this may be changed with the
103: .B \-m
104: flag).
105: The ``mark'' facility is not enabled by a facility field containing an asterisk.
106: The level ``none'' may be used to disable a particular facility.
107: For example,
108: .PP
109: .ti +5
110: *.debug;mail.none
111: .PP
112: Sends all messages
113: .I except
114: mail messages to the selected file.
115: .PP
116: The second part of each line describes where the message is to be logged
117: if this line is selected.
118: There are four forms:
119: .IP \(bu 3n
120: A filename (beginning with a leading slash).
121: The file will be opened in append mode.
122: .IP \(bu 3n
123: A hostname preceeded by an at sign (``@'').
124: Selected messages are forwarded to the
125: .I syslogd
126: on the named host.
127: .IP \(bu 3n
128: A comma separated list of users.
129: Selected messages are written to those users
130: if they are logged in.
131: .IP \(bu 3n
132: An asterisk.
133: Selected messages are written to all logged-in users.
134: .PP
135: Blank lines and lines beginning with `#' are ignored.
136: .PP
137: For example, the configuration file:
138: .PP
139: .nf
140: .ta 4m +\w'*.alert,auth.warning'u+3
141: kern,mark.debug /dev/console
142: *.notice;mail.info /var/log/maillog
143: *.crit /var/log/critical
144: kern.err @ucbarpa
145: *.emerg *
146: *.alert eric,kridle
147: *.alert;auth.warning ralph
148: .fi
149: .PP
150: logs all kernel messages
151: and 20 minute marks onto the system console,
152: all notice (or higher) level messages and all mail system messages
153: except debug messages
154: into the file /var/log/maillog,
155: and all critical messages
156: into /var/log/critical;
157: kernel messages of error severity or higher are forwarded
158: to ucbarpa.
159: All users will be informed of any emergency messages,
160: the users ``eric'' and ``kridle''
161: will be informed of any alert messages,
162: and the user ``ralph''
163: will be informed of any alert message,
164: or any warning message (or higher)
165: from the authorization system.
166: .PP
167: The flags are:
168: .TP 0.5i
169: .B \-f
170: Specify an alternate configuration file.
171: .TP
172: .B \-m
173: Select the number of minutes between mark messages.
174: .TP
175: .B \-d
176: Turn on debugging.
177: .PP
178: .I Syslogd
179: creates the file /var/run/syslog.pid, if possible,
180: containing a single line with its process id.
181: This can be used to kill or reconfigure
182: .I syslogd.
183: .PP
184: To bring
185: .I syslogd
186: down,
187: it should be sent a terminate signal (e.g. kill \`cat /var/run/syslog.pid\`).
188: .SH FILES
189: .ta \w'/etc/syslog.conf 'u
190: .nf
191: /etc/syslog.conf the configuration file
192: /var/run/syslog.pid the process id
193: /dev/log Name of the UNIX domain datagram log socket
194: /dev/klog The kernel log device
195: .fi
196: .SH SEE ALSO
197: logger(1), syslog(3)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.