Ed Ravin wrote:
> 
> In that case, we have a documentation bug - the fact that Sys::Syslog might
> crash the calling program with croak() is not mentioned in its man page.
> 
> Would you accept patches for a "nocroak" or "nofatal" option to be used
> in Sys::Syslog::openlog() to disable the fatal exit behavior?

I applied the following to bleadperl :

Change 25342 by [EMAIL PROTECTED] on 2005/08/31 15:14:28

        Document that Sys::Syslog::openlog might die.
        Fixes [perl #36848] Sys::Syslog::syslog kills program if syslogd not 
running 

Affected files ...

... //depot/perl/ext/Sys/Syslog/Syslog.pm#29 edit

Differences ...

==== //depot/perl/ext/Sys/Syslog/Syslog.pm#29 (text) ====

@@ -53,13 +53,15 @@
 
 =item openlog $ident, $logopt, $facility
 
+Opens the syslog.
 I<$ident> is prepended to every message.  I<$logopt> contains zero or
 more of the words I<pid>, I<ndelay>, I<nowait>.  The cons option is
 ignored, since the failover mechanism will drop down to the console
 automatically if all other media fail.  I<$facility> specifies the
 part of the system to report about, for example LOG_USER or LOG_LOCAL0:
 see your C<syslog(3)> documentation for the facilities available in
-your system.
+your system. This function will croak if it can't connect to the syslog
+daemon.
 
 B<You should use openlog() before calling syslog().>
 

Reply via email to