On Linux (and probably other unices), there is a file called /etc/syslog.conf which governs where your output will go. You can add a line like
local2.* /var/log/your_log_name
This defines the local2 category for your use.
Include Sys::Syslog in your script or module:
use Sys::Syslog qw(:DEFAULT setlogsock);
Then make a sub like this one:
sub syslog_event {
my ( $type, $message ) = @_;
Sys::Syslog::setlogsock( 'unix' );
openlog( 'daemon_name', '', 'local2' );
$message =~ s/\s+$//;
syslog( $type, $message );
closelog();
return();
} # END syslog_event
Then call syslog_event as needed passing it one of the allowed types and your message:
syslog_event( 'info', 'daemon starting' );
The types are taken from the system types. Look in
man 3 syslog
for 'level'. You'll see things like LOG_INFO, the type you need is everything after LOG_. You can use lower case if you like.
Phil
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.