[sanesecurity] Re: Clamd Crashes - another puzzle
- From: Arthur Dent <misc.lists@xxxxxxxxxxxxxxxx>
- To: sanesecurity@xxxxxxxxxxxxx
- Date: Mon, 2 Mar 2009 09:56:25 +0000
On Tue, Feb 24, 2009 at 02:03:45PM +0000, Arthur Dent wrote:
> On Tue, Feb 24, 2009 at 08:03:07AM -0500, Tom Shaw wrote:
> > Can I make a suggestion, for those of you that are having crashes try
> > disabling freshclam and unofficial scripts and then use the following
> > with cron or launchd
> >
> > #!/bin/sh
> > /usr/local/bin/freshclam
> > /path/to/unofficial-script-of-your-choice.sh
> >
> > If crashing stops for everyone, then there is a race condition between
> > reading and writing the signature files, If that is the case, both clamav
> > (I suspect that clamscan is just as vulnerable to this type of error as
> > clamd just the probability of it encountering the problem is much much
> > lower) and freshclam and unofficial updates need to be updated to share a
> > common api/protocol on locking and unlocking file access
>
> Good idea...
>
> I've just implemented this. No crashes yet. ..erm well it's only been 10
> minutes... but I'll keep you posted.
>
> Thanks
>
Well interestingly I just got my first crash since doing this - nearly a full
week - whereas previously I was getting on average 1 per day.
Mine is an admittedly low volume home machine, but nevertheless I think this
adds credence to the hypothesis that this is a timing related issue...
HTH
Mark
Other related posts:
