On Sat, 14 May 2005, Dennis Peterson wrote:
Clam runs fine when properly configured.
And it ran fine for me right up intil 0.85.
Are you asking the developers to
compensate for sloppy administration? I think for that you need a
No, what I'm asking for is if it runs one day with certain
Christopher X. Candreva said:
On Sat, 14 May 2005, Dennis Peterson wrote:
Clam runs fine when properly configured.
And it ran fine for me right up intil 0.85.
Are you asking the developers to
compensate for sloppy administration? I think for that you need a
No, what I'm asking for is if
May I add that it is really, really, really bad for clamav-milter to refuse
to run at all, just because it can't write to it's log file ?
I would much prefer it doing something and not logging then takeing down the
whole mail system.
==
On Sat, 14 May 2005, Christopher X. Candreva wrote:
May I add that it is really, really, really bad for clamav-milter to refuse
to run at all, just because it can't write to it's log file ?
I would much prefer it doing something and not logging then takeing down the
whole mail system.
If your
Christopher X. Candreva said:
May I add that it is really, really, really bad for clamav-milter to
refuse
to run at all, just because it can't write to it's log file ?
I would much prefer it doing something and not logging then takeing down
the
whole mail system.
On Sat, May 14, 2005 at 09:49:01AM -0700, Dennis Peterson wrote:
Christopher X. Candreva said:
May I add that it is really, really, really bad for clamav-milter to
refuse
to run at all, just because it can't write to it's log file ?
I would much prefer it doing something and not
Robert Stampfli said:
On Sat, May 14, 2005 at 09:49:01AM -0700, Dennis Peterson wrote:
Christopher X. Candreva said:
May I add that it is really, really, really bad for clamav-milter to
refuse
to run at all, just because it can't write to it's log file ?
I would much prefer it doing
On Sat, 14 May 2005, Robert Stampfli wrote:
clamav-milter does not have its own config file, so it steals
information from clamd.conf, and it now requires LogFile to be
defined there, even though it uses syslogging by default.
So, it appears I'm left with having to use a logfile for clamd,
to keep
