http://bugzilla.spamassassin.org/show_bug.cgi?id=4316
------- Additional Comments From [EMAIL PROTECTED] 2005-05-09 01:18 ------- (In reply to comment #6) > 'Is there any way to avoid that?' > > not unless we find an alternative to Sys::syslog. what amavisd does (iirc) is > log via a pipe to a /usr/bin/logger process, which may be more reliable. > > 'SA will need > to be able to handle breaks in communication with syslog without crashing' > > agreed... > > 'and it will need to be able to > resume logging once the environment allows' > > unfortunately, we cannot do that reliably due to Sys::Syslog shortcomings. > hence the SIGHUP. I suppose I could get shot for asking this, but given the syslog issue, is there any support for throwing in an option to log to a file? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
