http://bugzilla.spamassassin.org/show_bug.cgi?id=4316
------- Additional Comments From [EMAIL PROTECTED] 2005-05-09 01:01 ------- (In reply to comment #3) > pretty sure this is a dupe of bug 4237, fixed for 3.1.0. > summary: syslog-ng is seriously crappy. there's a patch in that bug. > > btw, yes, you need to restart (or SIGHUP) spamd after syslogd restart. > > *** This bug has been marked as a duplicate of 4237 *** Crappy or no (I only used it because of another package wanting it) SA will need to be able to handle breaks in communication with syslog without crashing (seemingly random unplanned crashes aren't fun) and it will need to be able to resume logging once the environment allows (otherwise logging is seriously handicapped and basicly undependable). This does look like a dup of that bug though. I did do some searching before opening this, but apparently still missed it. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
