logger man page on DigitalUNIX

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
DigitalUNIX logo
[printable version]

logger(1)							     logger(1)

       logger - Makes entries in the system log

       /usr/bin/logger	[-f  file] [-i] [-p[facility.]priority] [-t tag] [mes‐

       logger [-b] [message...]

       Interfaces documented on this reference page conform to industry	 stan‐
       dards as follows:

       logger:	XCU5.0

       Refer  to  the  standards(5)  reference page for more information about
       industry standards and associated tags.

       [Tru64 UNIX]  Logs the informational message to the binary event logger
       instead of the syslog() subroutine and enters information in the binary
       event log file.	The uerf command with the -r 250  option  reports  the
       informational  messages that are in the binary event log file, which is
       used for system maintenance and troubleshooting.	 The -b option	cannot
       be  used with any other options.	 [Tru64 UNIX]  Logs all lines in file.
       [Tru64 UNIX]  Logs the process ID (PID) of the logger process with each
       line.   [Tru64  UNIX]  Enters  the  message with the specified priority
       and, if specified, from the specified facility.

	      [Tru64 UNIX]  You can specify priority as either	an  alphabetic
	      string or its integer equivalent.	 You can specify the following
	      values for  the  priority	 variable:  [Tru64  UNIX]  (0)	[Tru64
	      UNIX]  The system is unusable.  (0) [Tru64 UNIX]	Action must be
	      taken immediately.  (1) [Tru64 UNIX]  Critical conditions.   (2)
	      [Tru64  UNIX]  Error  conditions.	  (3) [Tru64 UNIX]  (3) [Tru64
	      UNIX]  (4)  [Tru64  UNIX]	 Warning   conditions.	  (4)	[Tru64
	      UNIX]  Normal    but    significant   condition.	  (5)	[Tru64
	      UNIX]  Informational. (6)	 [Tru64	 UNIX]	Debug-level  messages.

	      [Tru64  UNIX]  You  can  also  specify  a value for the facility
	      variable, which indicates the source  of	the  event.   You  can
	      specify  facility	 as either an alphabetic string or its integer
	      equivalent.  The integer values appear in parentheses.  You  can
	      specify  the  following values for the facility variable: [Tru64
	      UNIX]  Kernel messages. (0) [Tru64 UNIX]	Random user-level mes‐
	      sages.  (8) [Tru64 UNIX]	Mail system. (16) [Tru64 UNIX]	System
	      daemons.	(24)  [Tru64  UNIX]  Security/authorization  messages.
	      (32) [Tru64 UNIX]	 (32) [Tru64 UNIX]  Messages syslogd generates
	      internally.  (40) [Tru64 UNIX]  Line  printer  subsystem.	  (48)
	      [Tru64  UNIX]  Network  news subsystem.  (56) [Tru64 UNIX]  UUCP
	      subsystem.   (64)	 [Tru64	 UNIX]	Clock  daemon.	 (72)	[Tru64
	      UNIX]  (128)  [Tru64  UNIX]  (136)  [Tru64  UNIX]	 (144)	[Tru64
	      UNIX]  (152)  [Tru64  UNIX]  (160)  [Tru64  UNIX]	 (168)	[Tru64
	      UNIX]  (176)  [Tru64  UNIX]  (184)  [Tru64  UNIX]	 Precedes each
	      entry in the log with tag.

       You can specify the message to be used for entries on the command  line
       or  with	 the -f file option, which specifies that each line in file be
       logged as an entry.  If you do not specify message or -f, logger	 reads
       standard input.

       The logger command makes the specified entries in the system log file.

       The logger command provides a program and shell script interface to the
       syslog() subroutine.  The file in which entries are made depends on the
       current	system	log  configuration;  see  syslog  and syslogd for more

       The effects of the environment variable LC_MESSAGES apply only to diag‐
       nostic messages generated by logger, and not to any messages written by
       the use of the command.

       The following exit values  are  returned:  Successful  completion.   An
       error occurred.

       To  log the system reboot, including the process ID of the process run‐
       ning logger,  enter: logger -i System rebooted To log each line in  the
       file  build.events with the tag trial build preceding them, enter: log‐
       ger -f build.events -t "trial build" The following commands are equiva‐
       lent and enter events of warning priority to the log: logger -p warning

       logger -p 4 The following commands are equivalent and enter events from
       the daemon facility of warning priority: logger -p daemon.warning

       logger -p 24.4 To specify the debug  priority  with  a  priority	 name,
       enter: logger -p debug my message

	      To  specify  the	debug  priority with a priority number, enter:
	      logger -p 7 my message To specify both debug  priority  and  the
	      user facility, enter: logger -p user.debug my message

	      To specify the same facility/priority pair using numeric values,
	      enter: logger -p 8.7 my message

	      You can also combine alphabetic and numeric specifications: log‐
	      ger -p user.7 my message logger -p 8.debug my message

       The  following  environment  variables  affect the execution of logger:
       Provides a default value for the	 internationalization  variables  that
       are  unset  or  null. If LANG is unset or null, the corresponding value
       from the default locale is used.	 If any	 of  the  internationalization
       variables contain an invalid setting, the utility behaves as if none of
       the variables had been defined.	If set to a  non-empty	string	value,
       overrides  the  values of all the other internationalization variables.
       Determines the locale for the interpretation of sequences of  bytes  of
       text  data as characters (for example, single-byte as opposed to multi-
       byte characters in arguments).  Determines the locale  for  the	format
       and  contents of diagnostic messages written to standard error.	Deter‐
       mines the location of message catalogues for the processing of  LC_MES‐

       Commands:  binlogd(8), syslogd(8), uerf(8)

       Functions:  syslog(3)

       Standards:  standards(5)


List of man pages available for DigitalUNIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net