Path: usenet.cise.ufl.edu!newsfeeds.nerdc.ufl.edu!headwall.stanford.edu!newsfeed.stanford.edu!logbridge.uoregon.edu!newspeer.monmouth.com!newsfeed.corridex.com!nntp2.savvis.net!inetarena.com!not-for-mail
From: Broc Seib <[email protected]>
Newsgroups: comp.lang.perl.announce,comp.lang.perl.modules
Subject: ANNOUNCE: Tie::Syslog
Followup-To: comp.lang.perl.modules
Date: 24 Sep 1999 12:35:28 GMT
Organization: vyking.com
Lines: 54
Approved: [email protected] (comp.lang.perl.announce)
Message-ID: <[email protected]>
NNTP-Posting-Host: halfdome.holdit.com
Keywords: tie syslog error capture logging perl CGI
X-Disclaimer: The "Approved" header verifies header information for article transmission and does not imply approval of content.
Xref: usenet.cise.ufl.edu comp.lang.perl.announce:365 comp.lang.perl.modules:13614

The module Tie::Syslog version 1.03 should soon be available on a CPAN
server near you. It is immediately available at http://vyking.com/CPAN.
Full documentation: http://vyking.com/CPAN/Tie-Syslog.html

-b


Tie::Syslog
===========

Copyright (C) 1999 Broc Seib. All rights reserved. This program
is free software; you can redistribute it and/or modify it under
the same terms as Perl itself.

Broc Seib, [email protected]


SYNOPSIS
========

 use Tie::Syslog;

 tie *MYLOG, 'Tie::Syslog', 'local0.error', 'my_program', 'pid';

 print MYLOG "I made an error."; ## this will be syslogged
 printf MYLOG "Error %d", 42;    ## syslog as "Error 42"

 untie *MYLOG;


DESCRIPTION
===========

This module allows you to tie a filehandle (output only) to
syslog. This becomes useful in general when you want to
capture any activity that happens on STDERR and see that it
is syslogged for later perusal. You can also create an arbitrary
filehandle, say LOG, and send stuff to syslog by printing to
this filehandle. This module depends on the Sys::Syslog module
to actually get info to syslog.

When used with STDERR, combined with the good habit of using
the perl -w switch, this module happens to be useful in
catching unexpected errors in any of your code, or team's
code. Tie::Syslog is pretty brain-dead. However, it can
become quite flexible if you investigate your options with
the actual syslog daemon. Syslog has a variety of options
available, including notifying console, logging to other
machines running syslog, or email support in the event of
Bad Things. Consult your syslog documentation to get
/etc/syslog.conf setup by your sysadmin and use Tie::Syslog
to get information into those channels.