On Fri, Oct 24, 2003 at 11:44:54AM +0200, Daniel Kraft wrote: > Package: perl > Version: 5.8.1-3 > Severity: normal > > The man page of Sys::Syslog suggests that its syslog function behaves > like syslog(3). However, an important difference is that -- unlike > syslog(3) -- it breaks if no syslogd is running. If this is intended > it should be documented and a reference to Unix::Syslog (package > libunix-syslog-perl) be added which behaves more like syslog(3).
Hi, this is also [rt.perl.org #36848]: http://rt.perl.org/rt3/Public/Bug/Display.html?id=36848 which was considered fixed by documenting it with change 25342, included in Perl 5.8.8. There's some more discussion in [rt.cpan.org #17316]: http://rt.cpan.org/Public/Bug/Display.html?id=17316 Quoting the Sys::Syslog upstream maintainer there: I'm not very fond of this request: the module works exactly as documented, and since a long time, even before it was documented to do so. Looking at the source of old versions, back to the one included in 5.003, openlog() would croak() if it couldn't connect to a syslog service, so accessing your request would mean changing a decade-old behaviour. By the way, why not using the classical Perl way to handle exceptions: eval { openlog(...) }; doe something_else() if $@; FWIW, Sys::Syslog 0.15 added a 'nofatal' option to turn this behaviour off. This is included in Perl 5.10.0, currently in Debian experimental. Please let us know if this satisfies your concerns, or if you still want to keep this bug open and wait for a reference to Unix::Syslog to be added as well. Cheers, -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
