MirBSD manpage: logger(1)

LOGGER(1)                    BSD Reference Manual                    LOGGER(1)


     logger - make entries in the system log


     logger [-is] [-f file] [-p pri] [-t tag] [message ...]


     The logger utility provides a shell command interface to the syslog(3)
     system log module.

     The options are as follows:

     -i       Log the process ID of the logger process with each line.

     -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 ex-
              ample, "-p local3.info" logs the message(s) as informational
              level in the local3 facility. The default is "user.notice".

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

     -t tag   Mark every line in the log with the specified tag.

     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 or >0 if an error occurred.


           $ logger System rebooted

           $ logger -p local0.notice -t HOSTIDM -f /dev/idmc


     syslog(3), syslogd(8)


     The logger utility conforms to IEEE Std 1003.2-1992 ("POSIX.2").


     Starting with MirBSD #10, the logger utility splits the data to log into
     chunks of 512 bytes each, so that further truncation does not occur un-
     less most of the input octets are vis(3) expanded, i.e. non-printable.

MirBSD #10-current            September 28, 2007                             1

Generated on 2022-12-24 01:00:14 by $MirOS: src/scripts/roff2htm,v 1.113 2022/12/21 23:14:31 tg Exp $ — This product includes material provided by mirabilos.

These manual pages and other documentation are copyrighted by their respective writers; their sources are available at the project’s CVSweb, AnonCVS and other mirrors. The rest is Copyright © 2002–2022 MirBSD.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.

Kontakt / Impressum & Datenschutzerklärung