xref: /netbsd-src/lib/libc/gen/syslog.3 (revision 1ffa7b76c40339c17a0fb2a09fac93f287cfc046)
1.\"	$NetBSD: syslog.3,v 1.17 2003/05/02 08:26:46 gmcgarry Exp $
2.\"
3.\" Copyright (c) 1985, 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.\"     @(#)syslog.3	8.1 (Berkeley) 6/4/93
35.\"
36.Dd March 14, 2001
37.Dt SYSLOG 3
38.Os
39.Sh NAME
40.Nm syslog ,
41.Nm vsyslog ,
42.Nm openlog ,
43.Nm closelog ,
44.Nm setlogmask
45.Nd control system log
46.Sh LIBRARY
47.Lb libc
48.Sh SYNOPSIS
49.In syslog.h
50.Ft void
51.Fn syslog "int priority" "const char *message" "..."
52.Ft void
53.Fn openlog "const char *ident" "int logopt" "int facility"
54.Ft void
55.Fn closelog void
56.Ft int
57.Fn setlogmask "int maskpri"
58.In stdarg.h
59.Ft void
60.Fn vsyslog "int priority" "const char *message" "va_list args"
61.Sh DESCRIPTION
62The
63.Fn syslog
64function
65writes
66.Fa message
67to the system message logger.
68The message is then written to the system console, log files,
69logged-in users, or forwarded to other machines as appropriate (See
70.Xr syslogd 8 ) .
71.Pp
72The message is identical to a
73.Xr printf 3
74format string, except that
75.Ql %m
76is replaced by the current error
77message.
78(As denoted by the global variable
79.Va errno ;
80see
81.Xr strerror 3 . )
82A trailing newline is added if none is present.
83.Pp
84The
85.Fn vsyslog
86function
87is an alternative form in which the arguments have already been captured
88using the variable-length argument facilities of
89.Xr varargs 3 .
90.Pp
91The message is tagged with
92.Fa priority .
93Priorities are encoded as a
94.Fa facility
95and a
96.Em level .
97The facility describes the part of the system
98generating the message.
99The level is selected from the following
100.Em ordered
101(high to low) list:
102.Bl -tag -width LOG_AUTHPRIV
103.It Dv LOG_EMERG
104A panic condition.
105This is normally broadcast to all users.
106.It Dv LOG_ALERT
107A condition that should be corrected immediately, such as a corrupted
108system database.
109.It Dv LOG_CRIT
110Critical conditions, e.g., hard device errors.
111.It Dv LOG_ERR
112Errors.
113.It Dv LOG_WARNING
114Warning messages.
115.It Dv LOG_NOTICE
116Conditions that are not error conditions,
117but should possibly be handled specially.
118.It Dv LOG_INFO
119Informational messages.
120.It Dv LOG_DEBUG
121Messages that contain information
122normally of use only when debugging a program.
123.El
124.Pp
125The
126.Fn openlog
127function
128provides for more specialized processing of the messages sent
129by
130.Fn syslog
131and
132.Fn vsyslog .
133The parameter
134.Fa ident
135is a string that will be prepended to every message.
136The
137.Fa logopt
138argument
139is a bit field specifying logging options, which is formed by
140.Tn OR Ns 'ing
141one or more of the following values:
142.Bl -tag -width LOG_AUTHPRIV
143.It Dv LOG_CONS
144If
145.Fn syslog
146cannot pass the message to
147.Xr syslogd 8
148it will attempt to write the message to the console
149.Pq Dq Pa /dev/console .
150.It Dv LOG_NDELAY
151Open the connection to
152.Xr syslogd 8
153immediately.
154Normally the open is delayed until the first message is logged.
155Useful for programs that need to manage the order in which file
156descriptors are allocated.
157.It Dv LOG_PERROR
158Write the message to standard error output as well to the system log.
159.It Dv LOG_PID
160Log the process id with each message: useful for identifying
161instantiations of daemons.  (This PID is placed within brackets
162between the ident and the message.)
163.El
164.Pp
165The
166.Fa facility
167parameter encodes a default facility to be assigned to all messages
168that do not have an explicit facility encoded:
169.Bl -tag -width LOG_AUTHPRIV
170.It Dv LOG_AUTH
171The authorization system:
172.Xr login 1 ,
173.Xr su 1 ,
174.Xr getty 8 ,
175etc.
176.It Dv LOG_AUTHPRIV
177The same as
178.Dv LOG_AUTH ,
179but logged to a file readable only by
180selected individuals.
181.It Dv LOG_CRON
182The cron daemon:
183.Xr cron 8 .
184.It Dv LOG_DAEMON
185System daemons, such as
186.Xr routed 8 ,
187that are not provided for explicitly by other facilities.
188.It Dv LOG_FTP
189The file transfer protocol daemon:
190.Xr ftpd 8 .
191.It Dv LOG_KERN
192Messages generated by the kernel.
193These cannot be generated by any user processes.
194.It Dv LOG_LPR
195The line printer spooling system:
196.Xr lpr 1 ,
197.Xr lpc 8 ,
198.Xr lpd 8 ,
199etc.
200.It Dv LOG_MAIL
201The mail system.
202.It Dv LOG_NEWS
203The network news system.
204.It Dv LOG_SYSLOG
205Messages generated internally by
206.Xr syslogd 8 .
207.It Dv LOG_USER
208Messages generated by random user processes.
209This is the default facility identifier if none is specified.
210.It Dv LOG_UUCP
211The uucp system.
212.It Dv LOG_LOCAL0
213Reserved for local use.
214Similarly for
215.Dv LOG_LOCAL1
216through
217.Dv LOG_LOCAL7 .
218.El
219.Pp
220The
221.Fn closelog
222function
223can be used to close the log file.
224.Pp
225The
226.Fn setlogmask
227function
228sets the log priority mask to
229.Fa maskpri
230and returns the previous mask.
231Calls to
232.Fn syslog
233with a priority not set in
234.Fa maskpri
235are rejected.
236The mask for an individual priority
237.Fa pri
238is calculated by the macro
239.Fn LOG_MASK pri ;
240the mask for all priorities up to and including
241.Fa toppri
242is given by the macro
243.Fn LOG_UPTO toppri .
244The default allows all priorities to be logged.
245.Sh RETURN VALUES
246The routines
247.Fn closelog ,
248.Fn openlog ,
249.Fn syslog
250and
251.Fn vsyslog
252return no value.
253.Pp
254The routine
255.Fn setlogmask
256always returns the previous log mask level.
257.Sh EXAMPLES
258.Bd -literal -offset indent -compact
259syslog(LOG_ALERT, "who: internal error 23");
260
261openlog("ftpd", LOG_PID | LOG_NDELAY, LOG_FTP);
262
263setlogmask(LOG_UPTO(LOG_ERR));
264
265syslog(LOG_INFO, "Connection from host %d", CallingHost);
266
267syslog(LOG_INFO|LOG_LOCAL2, "foobar error: %m");
268.Ed
269.Sh SEE ALSO
270.Xr logger 1 ,
271.Xr syslogd 8
272.Sh HISTORY
273These
274functions appeared in
275.Bx 4.2 .
276.Sh CAVEATS
277It is important never to pass a string with user-supplied data as a
278format without using
279.Ql %s .
280An attacker can put format specifiers in the string to mangle your stack,
281leading to a possible security hole.
282This holds true even if you have built the string
283.Dq by hand
284using a function like
285.Fn snprintf ,
286as the resulting string may still contain user-supplied conversion specifiers
287for later interpolation by
288.Fn syslog .
289.Pp
290Always be sure to use the proper secure idiom:
291.Bd -literal -offset indent
292syslog(priority, "%s", string);
293.Ed
294