On Fri, Aug 19, 2005 at 04:37:43PM +0100, Brian Morrison wrote:
> On Fri, 19 Aug 2005 17:31:17 +0200 in
> [EMAIL PROTECTED] Marc Haber
> <[EMAIL PROTECTED]> wrote:
> 
> > On Fri, Aug 19, 2005 at 08:26:05AM -0700, Todd Lyons wrote:
> > > What he needs to do is write a perl script that connects to the
> > > local clamd socket and prints "VERSION" and then look at the
> > > resulting reply.
> > 
> > NACK, clamd accesses the database file as well when VERSION is
> > received on the socket, and reports back immediately the new database
> > number even if it has not been loaded according to the log.
> 
> Except that then it will have been loaded and this information will
> have been entered in the log.

Looks like you have more faith in things than I have. All software
sucks, why should clamav be the exception?

> Clamd only reloads the database when it
> has some work to do, clamdscan -V being "some work" obviously.

NACK, clamdscan -V doesn't talk to the daemon _at_ _all_, so this
doesn't qualify as "some work".

> You might ask the developers to change the database reloaded message to
> include the version number, as long as that doesn't break anything I
> don't see why this should not be done.

The developers don't at least read here? Well, at least Debian has a
bug (#323803) about it.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html

Reply via email to