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
On Wed, Aug 31, 2005 at 09:01:57AM -0700, Rafael Garcia-Suarez via RT wrote:
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
On Wed, Aug 10, 2005 at 12:21:49PM -0400, Ed Ravin wrote:
I submit that this is a design bug - no other syslog() library behaves
this way, especially not the C library that Syslog.pm is based on.
Sys::Syslog::syslog() should return an error and let the user deal
with it (which would be an
On Thu, Aug 11, 2005 at 01:52:35AM -0700, Nicholas Clark via RT wrote:
On Wed, Aug 10, 2005 at 12:21:49PM -0400, Ed Ravin wrote:
I submit that this is a design bug - no other syslog() library behaves
this way, especially not the C library that Syslog.pm is based on.
Sys::Syslog::syslog()
On Tue, Aug 09, 2005 at 04:30:32PM -0700, eravin @ panix. com wrote:
connect: No such file or directory (SOCK_DGRAM after trying SOCK_STREAM)
at perlprog line NNN
Where the offending line is something like:
syslog(notice, SHUTDOWN: $sig);
The offending line is in a signal
On Wed, Aug 10, 2005 at 01:32:04AM -0700, Nicholas Clark via RT wrote:
On Tue, Aug 09, 2005 at 04:30:32PM -0700, eravin @ panix. com wrote:
connect: No such file or directory (SOCK_DGRAM after trying SOCK_STREAM)
at perlprog line NNN
Where the offending line is something like:
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #36848]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=36848
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help
