With syslog, people tend not to include the REASON of the message
in the logs, because that is already used to determine the destination
of the message.
- accept => REASONS
- charset => CHARSET
- Translate the text-strings into the specified charset, otherwise the
sysadmin may get unreadable text.
- facility => STRING
- The possible values for this depend (a little) on the system. POSIX
only defines
user
, and local0
up to local7
.
- flags => STRING
- Any combination of flags as defined by Sys::Syslog, for instance
pid
, ndelay
, and nowait
.
- format => CODE
- [1.10] With a CODE reference you get your hands on the text before
it gets sent to syslog. The three parameters are: the (translated) text,
the related text domain object, and the message object. You may want to
use context information from the latter.
[1.19] After the three positional parameters, there may be a list of
pairs (named parameters) with additional info. This may contain a
location
with an ARRAY of information produced by caller() about the
origin of the exception.
- format_reason => 'UPPERCASE'|'LOWERCASE'|'UCFIRST'|'IGNORE'|CODE
- identity => STRING
- include_domain => BOOLEAN
- [1.00] Include the text-domain of the message in each logged message.
- locale => LOCALE
- logsocket => 'unix'|'inet'|'stream'|HASH
- If specified, the log socket type will be initialized to this before
openlog()
is called. If not specified, the system default is used.
- mode => 'NORMAL'|'VERBOSE'|'ASSERT'|'DEBUG'|0..3
- to_prio => ARRAY-of-PAIRS
- See reasonToPrio().