xref: /freebsd/lib/libc/gen/syslog.3 (revision 9f23cbd6cae82fd77edfad7173432fa8dccd0a95)
1.\" Copyright (c) 1985, 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. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\"     @(#)syslog.3	8.1 (Berkeley) 6/4/93
29.\" $FreeBSD$
30.\"
31.Dd July 3, 2023
32.Dt SYSLOG 3
33.Os
34.Sh NAME
35.Nm syslog ,
36.Nm vsyslog ,
37.Nm openlog ,
38.Nm closelog ,
39.Nm setlogmask
40.Nd control system log
41.Sh LIBRARY
42.Lb libc
43.Sh SYNOPSIS
44.In syslog.h
45.Ft void
46.Fn syslog "int priority" "const char *message" "..."
47.Ft void
48.Fn openlog "const char *ident" "int logopt" "int facility"
49.Ft void
50.Fn closelog void
51.Ft int
52.Fn setlogmask "int maskpri"
53.In syslog.h
54.In stdarg.h
55.Ft void
56.Fn vsyslog "int priority" "const char *message" "va_list args"
57.Sh DESCRIPTION
58The
59.Fn syslog
60function
61writes
62.Fa message
63to the system message logger.
64The message is then written to the system console, log files,
65logged-in users, or forwarded to other machines as appropriate.
66(See
67.Xr syslogd 8 . )
68.Pp
69The message is identical to a
70.Xr printf 3
71format string, except that
72.Ql %m
73is replaced by the current error
74message.
75(As denoted by the global variable
76.Va errno ;
77see
78.Xr strerror 3 . )
79A trailing newline is added if none is present.
80.Pp
81The
82.Fn vsyslog
83function
84is an alternate form in which the arguments have already been captured
85using the variable-length argument facilities of
86.Xr stdarg 3 .
87.Pp
88The message is tagged with
89.Fa priority .
90Priorities are encoded as a
91.Fa facility
92and a
93.Em level .
94The facility describes the part of the system
95generating the message.
96The level is selected from the following
97.Em ordered
98(high to low) list:
99.Bl -tag -width LOG_AUTHPRIV
100.It Dv LOG_EMERG
101A panic condition.
102This is normally broadcast to all users.
103.It Dv LOG_ALERT
104A condition that should be corrected immediately, such as a corrupted
105system database.
106.It Dv LOG_CRIT
107Critical conditions, e.g., hard device errors.
108.It Dv LOG_ERR
109Errors.
110.It Dv LOG_WARNING
111Warning messages.
112.It Dv LOG_NOTICE
113Conditions that are not error conditions,
114but should possibly be handled specially.
115.It Dv LOG_INFO
116Informational messages.
117.It Dv LOG_DEBUG
118Messages that contain information
119normally of use only when debugging a program.
120.El
121.Pp
122The
123.Fn openlog
124function
125provides for more specialized processing of the messages sent
126by
127.Fn syslog
128and
129.Fn vsyslog .
130The
131.Fa ident
132argument
133is a string that will be prepended to every message.
134It may be formatted as
135.Fa ident[N]
136in which case decimal number
137.Fa N
138replaces the process id within messages.
139The
140.Fa logopt
141argument
142is a bit field specifying logging options, which is formed by
143.Tn OR Ns 'ing
144one or more of the following values:
145.Bl -tag -width LOG_AUTHPRIV
146.It Dv LOG_CONS
147If
148.Fn syslog
149cannot pass the message to
150.Xr syslogd 8
151it will attempt to write the message to the console
152.Pq Dq Pa /dev/console .
153.It Dv LOG_NDELAY
154Open the connection to
155.Xr syslogd 8
156immediately.
157Normally the open is delayed until the first message is logged.
158Useful for programs that need to manage the order in which file
159descriptors are allocated.
160.It Dv LOG_PERROR
161Write the message to standard error output as well to the system log.
162.It Dv LOG_PID
163Log the process id with each message: useful for identifying
164instantiations of daemons.
165On
166.Fx ,
167this option is enabled by default and cannot be disabled.
168.El
169.Pp
170The
171.Fa facility
172argument encodes a default facility to be assigned to all messages
173that do not have an explicit facility encoded:
174.Bl -tag -width LOG_AUTHPRIV
175.It Dv LOG_AUTH
176The authorization system:
177.Xr login 1 ,
178.Xr su 1 ,
179.Xr getty 8 ,
180etc.
181.It Dv LOG_AUTHPRIV
182The same as
183.Dv LOG_AUTH ,
184but logged to a file readable only by
185selected individuals.
186.It Dv LOG_CONSOLE
187Messages written to
188.Pa /dev/console
189by the kernel console output driver.
190.It Dv LOG_CRON
191The cron daemon:
192.Xr cron 8 .
193.It Dv LOG_DAEMON
194System daemons, such as
195.Xr routed 8 ,
196that are not provided for explicitly by other facilities.
197.It Dv LOG_FTP
198The file transfer protocol daemons:
199.Xr ftpd 8 ,
200.Xr tftpd 8 .
201.It Dv LOG_KERN
202Messages generated by the kernel.
203These cannot be generated by any user processes.
204.It Dv LOG_LPR
205The line printer spooling system:
206.Xr lpr 1 ,
207.Xr lpc 8 ,
208.Xr lpd 8 ,
209etc.
210.It Dv LOG_MAIL
211The mail system.
212.It Dv LOG_NEWS
213The network news system.
214.It Dv LOG_NTP
215The network time protocol system.
216.It Dv LOG_SECURITY
217Security subsystems, such as
218.Xr ipfw 4 .
219.It Dv LOG_SYSLOG
220Messages generated internally by
221.Xr syslogd 8 .
222.It Dv LOG_USER
223Messages generated by random user processes.
224This is the default facility identifier if none is specified.
225.It Dv LOG_UUCP
226The uucp system.
227.It Dv LOG_LOCAL0
228Reserved for local use.
229Similarly for
230.Dv LOG_LOCAL1
231through
232.Dv LOG_LOCAL7 .
233.El
234.Pp
235The
236.Fn closelog
237function
238can be used to close the log file.
239.Pp
240The
241.Fn setlogmask
242function
243sets the log priority mask to
244.Fa maskpri
245and returns the previous mask.
246Calls to
247.Fn syslog
248with a priority not set in
249.Fa maskpri
250are rejected.
251The mask for an individual priority
252.Fa pri
253is calculated by the macro
254.Fn LOG_MASK pri ;
255the mask for all priorities up to and including
256.Fa toppri
257is given by the macro
258.Fn LOG_UPTO toppri ; .
259The default allows all priorities to be logged.
260.Sh RETURN VALUES
261The routines
262.Fn closelog ,
263.Fn openlog ,
264.Fn syslog
265and
266.Fn vsyslog
267return no value.
268.Pp
269The routine
270.Fn setlogmask
271always returns the previous log mask level.
272.Sh EXAMPLES
273.Bd -literal -offset indent -compact
274syslog(LOG_ALERT, "who: internal error 23");
275
276openlog("ftpd", LOG_PID | LOG_NDELAY, LOG_FTP);
277
278setlogmask(LOG_UPTO(LOG_ERR));
279
280syslog(LOG_INFO, "Connection from host %d", CallingHost);
281
282syslog(LOG_ERR|LOG_LOCAL2, "foobar error: %m");
283.Ed
284.Sh SEE ALSO
285.Xr logger 1 ,
286.Xr syslogd 8
287.Sh HISTORY
288These
289functions appeared in
290.Bx 4.2 .
291.Sh BUGS
292Never pass a string with user-supplied data as a format without using
293.Ql %s .
294An attacker can put format specifiers in the string to mangle your stack,
295leading to a possible security hole.
296This holds true even if the string was built using a function like
297.Fn snprintf ,
298as the resulting string may still contain user-supplied conversion specifiers
299for later interpolation by
300.Fn syslog .
301.Pp
302Always use the proper secure idiom:
303.Pp
304.Dl syslog(priority, \*q%s\*q, string);
305