Name

logger — a shell command interface to the syslog(3) system log module

Synopsis

logger [−isd] [ −f file ] [ −p pri ] [ −t tag ] [ −u socket ] [ message... ]

DESCRIPTION

Logger makes entries in the system log. It provides a shell command interface to the syslog(3) system log module.

Options:

−i

Log the process id of the logger process with each line.

−s

Log the message to standard error, as well as the system log.

−f file

Log the specified file.

−p pri

Enter the message with the specified priority. The priority may be specified numerically or as a ``facility.level'' pair. For example, ``−p local3.info'' logs the message(s) as informational level in the local3 facility. The default is ``user.notice.''

−t tag

Mark every line in the log with the specified tag.

−u sock

Write to socket as specified with socket instead of builtin syslog routines.

−d

Use a datagram instead of a stream connection to this socket.

−−

End the argument list. This is to allow the message to start with a hyphen (−).

message

Write the message to log; if not specified, and the −f flag is not provided, standard input is logged.

The logger utility exits 0 on success, and >0 if an error occurs.

Valid facility names are: auth, authpriv (for security information of a sensitive nature), cron, daemon, ftp, kern, lpr, mail, news, security (deprecated synonym for auth), syslog, user, uucp, and local0 to local7, inclusive.

Valid level names are): alert, crit, debug, emerg, err, error (deprecated synonym for err), info, notice, panic (deprecated synonym for emerg), warning, warn (deprecated synonym for warning). For the priority order and intended purposes of these levels, see syslog(3).

EXAMPLES

logger System rebooted

logger −p local0.notice −t HOSTIDM −f /dev/idmc

SEE ALSO

syslog(3), syslogd(8)

STANDARDS

The logger command is expected to be IEEE Std 1003.2 (“POSIX.2”) compatible.


  Copyright (c) 1983, 1990, 1993
The Regents of the University of California.  All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
   must display the following acknowledgement:
This product includes software developed by the University of
California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors
   may be used to endorse or promote products derived from this software
   without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

(#)logger.1 8.1 (Berkeley) 6/6/93

Section on valid facitily and level strings added by
and1000debian.org, 26 Oct 1997.