Hello,
Version of clamav-milter?
clamav-milter --version
ClamAV version 0.88.3, clamav-milter version 0.88.3
but i use clamd --version
ClamAV 0.88.4/2024/Wed Oct 11 10:53:09 2006
because I thought that the problem appeared in clamav-milter 0.88.4
and downgraded just that component.
Ope
On Fri, 06 Oct 2006, 11:48 GMT+01 Nigel Horne wrote:
> Tomasz Kojm wrote:
>> This doesn't answer my question. Does "LogFileUnlock yes" added to
>> freshclam.conf solve the issue?
> If freshclam.conf also supports
> LogFileUnlock then that should be documented in the freshclam.conf that
> is incl
On Fri, 06 Oct 2006 11:48:40 +0100
Nigel Horne <[EMAIL PROTECTED]> wrote:
> > This doesn't answer my question. Does "LogFileUnlock yes" added to
> > freshclam.conf solve the issue?
>
> That's because
> 1) LogFileUnlock goes in clamd.conf. If freshclam.conf also supports
> LogFileUnlock then that
Tomasz Kojm wrote:
On Fri, 06 Oct 2006 11:32:52 +0100
Nigel Horne <[EMAIL PROTECTED]> wrote:
Tomasz Kojm wrote:
On Fri, 06 Oct 2006 10:59:58 +0100
Nigel Horne <[EMAIL PROTECTED]> wrote:
I have found that starting concurrent copies of freshclam can give logg()
errors, but I'm yet to find it r
On Fri, 06 Oct 2006 11:32:52 +0100
Nigel Horne <[EMAIL PROTECTED]> wrote:
> Tomasz Kojm wrote:
> > On Fri, 06 Oct 2006 10:59:58 +0100
> > Nigel Horne <[EMAIL PROTECTED]> wrote:
> >
> >> I have found that starting concurrent copies of freshclam can give logg()
> >> errors, but I'm yet to find it r
Tomasz Kojm wrote:
On Fri, 06 Oct 2006 10:59:58 +0100
Nigel Horne <[EMAIL PROTECTED]> wrote:
I have found that starting concurrent copies of freshclam can give logg()
errors, but I'm yet to find it resulting in anything crashing. The logg
problems are, I suspect, because of issues in the logfil
On Fri, 06 Oct 2006 10:59:58 +0100
Nigel Horne <[EMAIL PROTECTED]> wrote:
> I have found that starting concurrent copies of freshclam can give logg()
> errors, but I'm yet to find it resulting in anything crashing. The logg
> problems are, I suspect, because of issues in the logfile locking code,
I have found that starting concurrent copies of freshclam can give logg()
errors, but I'm yet to find it resulting in anything crashing. The logg
problems are, I suspect, because of issues in the logfile locking code, which
it's true should be addressed.
[EMAIL PROTECTED] freshclam]# freshclam
Dilyan Palauzov wrote:
Hello,
On my system clamav-milter crasesh from time to time (disappears,
issues clamfi_close, whatever). This happens usually during spam attacks
(high load).
On my system the cron executes everything twice, instead of once.
Thus freshclam is executed twice,
Hello,
On my system clamav-milter crasesh from time to time (disappears,
issues clamfi_close, whatever). This happens usually during spam attacks
(high load).
On my system the cron executes everything twice, instead of once. Thus
freshclam is executed twice, sometimes within a very sm
10 matches
Mail list logo