Mixed news on the spamd/syslog-ng front:
I've tracked the problem down pretty far. If syslog-ng is restarted
after a Sys::Syslog::connect(), and then &syslog() is called, the
process will die with "Broken Pipe".
It does not appear that this can be caught. I tried wrapping it in an
eval {} and it still killed the process.
I'm also not sure where it's coming from. I grepped through
/usr/bin/perl and all modules, manpages and included libraries that I
could find, looking for "Broken Pipe".
I found two ways to "fix" it.
1) put &closelog at the end of &logmsg. This is clearly inefficient.
2) use "inet" sockets rather than "unix" sockets for syslog.
Presumably, you chose "unix" for a reason, though.
I can't imagine why this would be a problem for syslog-ng but not
syslog. What could they possibly be doing differently?
Any thoughts?
-Michael
--
Michael Stenner Office Phone: 919-660-2513
Duke University, Dept. of Physics [EMAIL PROTECTED]
Box 90305, Durham N.C. 27708-0305
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
