Jason L Tibbitts <email@example.com> writes:
> At least we check and tell you what you're missing. But this very issue
> is why I earlier asked about syslog removing support (since this pain is
> only required for Syslog.pm) and everyone wants that to stay. If syslog
> stays, the pain stays as well. It might be nice to just turn off syslog
> support if it isn't found (or configurably otherwise); if someone wishes
> to work on this, it sure would be a big help.
The better approach is to move to an XS module for syslog. One has
already been written, and at some point will be included in core as
replacement for the current Sys::Syslog (which doesn't work quite right on
Solaris under some installations). The XS module will just call the C
library functions rather than doing all the ugliness that Sys::Syslog does
now (falling back on the UDP and socket stuff if the C library doesn't
have those calls).
Russ Allbery (firstname.lastname@example.org) <URL:http://www.eyrie.org/~eagle/>