closelog, openlog, syslog, vsyslog - send messages to the system logger
void openlog(const char *
priority, const char
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
vsyslog(): Since glibc 2.19: _DEFAULT_SOURCE Glibc 2.19 and earlier: _BSD_SOURCE
openlog() opens a connection to the system logger for a program.
The string pointed to by
ident is prepended to every
message, and is typically set to the program name. If
NULL, the program name is used. (POSIX.1-2008 does not specify the
ident is NULL.)
option argument specifies flags which control the
operation of openlog() and subsequent calls to
facility argument establishes a
default to be used if none is specified in subsequent calls to
syslog(). The values that may be specified for
facility are described below.
priority argument is formed by ORing together a
facility value and a
level value (described below). If
facility value is ORed into
priority, then the
default value set by openlog() is used, or, if there
was no preceding openlog() call, a default of
LOG_USER is employed.
The remaining arguments are a
format, as in
printf(3), and any arguments required by the
format, except that the two-character sequence
%m will be replaced by the error message string
errno). The format string need not include a
terminating newline character.
option argument to openlog() is a bit
mask constructed by ORing together any of the following values:
Write directly to the system console if there is an error while sending to the system logger.
Open the connection immediately (normally, the connection is opened when the first message is logged). This may be useful, for example, if a subsequent chroot(2) would make the pathname used internally by the logging facility unreachable.
Don't wait for child processes that may have been created while logging the message. (The GNU C library does not create a child process, so this option has no effect on Linux.)
The converse of LOG_NDELAY; opening of the connection is delayed until syslog() is called. (This is the default, and need not be specified.)
(Not in POSIX.1-2001 or POSIX.1-2008.) Also log the message to
Include the caller's PID with each message.
facility argument is used to specify what type of
program is logging the message. This lets the configuration file specify
that messages from different facilities will be handled differently.
security/authorization messages (private)
clock daemon (cron and at)
system daemons without separate facility value
kernel messages (these can't be generated from user processes)
reserved for local use
line printer subsystem
USENET news subsystem
messages generated internally by syslogd(8)
generic user-level messages
This determines the importance of the message. The levels are, in order of decreasing importance:
system is unusable
action must be taken immediately
normal, but significant, condition
The function setlogmask(3) can be used to restrict logging to specified levels only.
POSIX.1-2001 specifies only the LOG_USER and
LOG_LOCAL* values for
facility. However, with
the exception of LOG_AUTHPRIV and
LOG_FTP, the other
facility values appear on
most UNIX systems.
The LOG_PERROR value for
option is not
specified by POSIX.1-2001 or POSIX.1-2008, but is available in most
versions of UNIX.
ident in the call of openlog()
is probably stored as-is. Thus, if the string it points to is changed,
syslog() may start prepending the changed string, and
if the string it points to ceases to exist, the results are undefined.
Most portable is to use a string constant.
Never pass a string with user-supplied data as a format, use the following instead:
syslog(priority, "%s", string);
This page is part of release 5.10 of the Linux
project. A description of the project, information about reporting bugs,
and the latest version of this page, can be found at