Re: Sys::Syslog skips the first event

Am I using Sys::Syslog wrongly ... I know that the man page asks us -- twice -- not to run setlogsock

It seems you've answered your own question there... although it's too bad that it is not evident from the documentation or version history as to why setlogsock has been discouraged since v0.18 (that was almost 10 years ago). Just a wild guess: maybe a Wireshark trace could give you a hint.

Have you looked into any of the other Syslog modules?

Comment on Re: Sys::Syslog skips the first event Download Code

Replies are listed 'Best First'.
Re^2: Sys::Syslog skips the first event by MarkusLaker (Beadle) on Jun 10, 2015 at 15:16 UTC
The documentation hints that the reason for not using setlogsock is that some people were using it without knowing what it did, and were making their code less reliable, rather than more so, by routinely writing setlogsock('unix'). Thanks for the pointers to other Syslog modules. I'd rather not resort to them because it would impose more work on the customers who have to run this program, but I'll go there (or just write the subset of syslogging that I actually need) if I can't make the program work acceptably in any other way.	[reply]

Replies are listed 'Best First'.

Re^2: Sys::Syslog skips the first event
by MarkusLaker (Beadle) on Jun 10, 2015 at 15:16 UTC

Thanks for the pointers to other Syslog modules. I'd rather not resort to them because it would impose more work on the customers who have to run this program, but I'll go there (or just write the subset of syslogging that I actually need) if I can't make the program work acceptably in any other way.

[reply]