The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

NAME

Log::Dispatch::Syslog - Object for logging to system log.

SYNOPSIS

  use Log::Dispatch::Syslog;

  my $file = Log::Dispatch::Syslog->new( name      => 'file1',
                                         min_level => 'info',
                                         ident     => 'Yadda yadda' );

  $file->log( level => 'emerg', message => "Time to die." );

DESCRIPTION

This module provides a simple object for sending messages to the system log (via UNIX syslog calls).

METHODS

  • new(%PARAMS)

    This method takes a hash of parameters. The following options are valid:

  • -- name ($)

    The name of the object. Required.

  • -- min_level ($)

    The minimum logging level this object will accept. See the Log::Dispatch documentation for more information. Required.

  • -- max_level ($)

    The maximum logging level this obejct will accept. See the Log::Dispatch documentation for more information. This is not required. By default the maximum is the highest possible level (which means functionally that the object has no maximum).

  • -- ident ($)

    This string will be prepended to all messages in the system log. Defaults to $0.

  • -- logopt ($)

    A string containing the log options (separated by any separator you like). Valid options are 'cons', 'pid', 'ndelay', and 'nowait'. See the openlog(3) and Sys::Syslog docs for more details. I would suggest not using 'cons' but instead using Log::Dispatch::Screen. Defaults to ''.

  • -- facility ($)

    Specifies what type of program is doing the logging to the system log. Valid options are 'auth', 'authpriv', 'cron', 'daemon', 'kern', 'local0' through 'local7', 'mail, 'news', 'syslog', 'user', 'uucp'. Defaults to 'user'

  • -- socket ($)

    Tells what type of socket to use for sending syslog messages. Valid options are 'unix' or 'inet'. Defaults to 'inet'.

  • -- callbacks( \& or [ \&, \&, ... ] )

    This parameter may be a single subroutine reference or an array reference of subroutine references. These callbacks will be called in the order they are given and passed a hash containing the following keys:

     ( message => $log_message, level => $log_level )

    The callbacks are expected to modify the message and then return a single scalar containing that modified message. These callbacks will be called when either the log or log_to methods are called and will only be applied to a given message once.

  • log_message( message => $ )

    Sends a message to the appropriate output. Generally this shouldn't be called directly but should be called through the log() method (in Log::Dispatch::Output).

AUTHOR

Dave Rolsky, <autarch@urth.org>

SEE ALSO

Log::Dispatch, Log::Dispatch::ApacheLog, Log::Dispatch::Email, Log::Dispatch::Email::MailSend, Log::Dispatch::Email::MailSendmail, Log::Dispatch::Email::MIMELite, Log::Dispatch::File, Log::Dispatch::Handle, Log::Dispatch::Output, Log::Dispatch::Screen

8 POD Errors

The following errors were encountered while parsing the POD:

Around line 104:

Expected '=item *'

Around line 108:

Expected '=item *'

Around line 113:

Expected '=item *'

Around line 120:

Expected '=item *'

Around line 125:

Expected '=item *'

Around line 133:

Expected '=item *'

Around line 140:

Expected '=item *'

Around line 145:

Expected '=item *'