On Fri, 19 Aug 2005 17:46:17 +0200 in
[EMAIL PROTECTED] Marc Haber
<[EMAIL PROTECTED]> wrote:
> > 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
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 th
On Fri, 19 Aug 2005 17:37:19 +0200 in
[EMAIL PROTECTED] Marc Haber
<[EMAIL PROTECTED]> wrote:
> On Fri, Aug 19, 2005 at 04:31:55PM +0100, Brian Morrison wrote:
> > Does clamdscan do the same thing then?
> >
> > I've just tried that and it reports a version, presumably supplied
> > by clamd.
>
>
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
> > resul
On Fri, Aug 19, 2005 at 04:31:55PM +0100, Brian Morrison wrote:
> Does clamdscan do the same thing then?
>
> I've just tried that and it reports a version, presumably supplied by
> clamd.
clamdscan -V doesn't communicate with the daemon at all, it opens the
configuration file, presumably finds ou
On Fri, 19 Aug 2005 08:26:05 -0700 in [EMAIL PROTECTED]
Todd Lyons <[EMAIL PROTECTED]> wrote:
> Brian Morrison wanted us to know:
>
> >> And it would be nice to obtain the currently loaded database from
> >the > daemon without having to parse the log files.
> >clamscan -V
>
> That's not what he'
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 r
Brian Morrison wanted us to know:
>> And it would be nice to obtain the currently loaded database from the
>> daemon without having to parse the log files.
>clamscan -V
That's not what he's asking. That only tells you what version of the
database clamscan finds and loads when you run it. That d
On Fri, 19 Aug 2005 17:06:03 +0200 in
[EMAIL PROTECTED] Marc Haber
<[EMAIL PROTECTED]> wrote:
> Does your clamav daemon say from which file the database is being
> loaded? Mine only states the directory, and it doesn't log which
> version the database is.
Oh, and I should have said that my /va
On Fri, 19 Aug 2005 17:06:03 +0200 in
[EMAIL PROTECTED] Marc Haber
<[EMAIL PROTECTED]> wrote:
> On Fri, Aug 19, 2005 at 03:54:11PM +0100, Brian Morrison wrote:
> > My freshclam/clamd setup logs to syslog and indicates when freshclam
> > retrieves an updated database and when clamd reloads the data
On Fri, Aug 19, 2005 at 03:54:11PM +0100, Brian Morrison wrote:
> My freshclam/clamd setup logs to syslog and indicates when freshclam
> retrieves an updated database and when clamd reloads the database
> following the notification from freshclam.
Does your clamav daemon say from which file the da
On Fri, Aug 19, 2005 at 11:44:24AM -0300, Julio Maidanik wrote:
> Marc Haber wrote:
> > On Fri, Aug 19, 2005 at 07:10:39AM -0700, Dennis Peterson wrote:
> >> And you're certain the database has not been reloaded while you're
> >> examining this?
> >
> > Which puts us back to the beginning. How do I
On Fri, 19 Aug 2005 16:15:17 +0200 in
[EMAIL PROTECTED] Marc Haber
<[EMAIL PROTECTED]> wrote:
> On Fri, Aug 19, 2005 at 07:10:39AM -0700, Dennis Peterson wrote:
> > And you're certain the database has not been reloaded while you're
> > examining this?
>
> Which puts us back to the beginning. How
Marc Haber wrote:
> On Fri, Aug 19, 2005 at 07:10:39AM -0700, Dennis Peterson wrote:
>> And you're certain the database has not been reloaded while you're
>> examining this?
>
> Which puts us back to the beginning. How do I find out _for_ _sure_
> which database version clamav-daemon actually wor
On Fri, Aug 19, 2005 at 07:10:39AM -0700, Dennis Peterson wrote:
> And you're certain the database has not been reloaded while you're
> examining this?
Which puts us back to the beginning. How do I find out _for_ _sure_
which database version clamav-daemon actually works at a given moment?
Greeti
Marc Haber said:
> On Fri, Aug 19, 2005 at 12:09:36AM -0700, Dennis Peterson wrote:
>> Marc Haber said:
>> > On Thu, Aug 18, 2005 at 11:30:38AM -0500, René Berber wrote:
>> >> Marc Haber wrote:
>> >> > the clamd docs say quite clearly that it is necessary to either
>> send
>> >> > the RELOAD comman
On Fri, Aug 19, 2005 at 12:09:36AM -0700, Dennis Peterson wrote:
> Marc Haber said:
> > On Thu, Aug 18, 2005 at 11:30:38AM -0500, René Berber wrote:
> >> Marc Haber wrote:
> >> > the clamd docs say quite clearly that it is necessary to either send
> >> > the RELOAD command to the daemon or to send
Marc Haber said:
> On Thu, Aug 18, 2005 at 11:30:38AM -0500, René Berber wrote:
>> Marc Haber wrote:
>> > the clamd docs say quite clearly that it is necessary to either send
>> > the RELOAD command to the daemon or to send SIGUSR2 to the daemon to
>> > have it reload the database.
>> >
>> > Howeve
On Thu, Aug 18, 2005 at 11:30:38AM -0500, René Berber wrote:
> Marc Haber wrote:
> > the clamd docs say quite clearly that it is necessary to either send
> > the RELOAD command to the daemon or to send SIGUSR2 to the daemon to
> > have it reload the database.
> >
> > However, the VERSION command a
Marc Haber wrote:
> Hi,
>
> the clamd docs say quite clearly that it is necessary to either send
> the RELOAD command to the daemon or to send SIGUSR2 to the daemon to
> have it reload the database.
>
> However, the VERSION command and clamdscan -V report the new database
> version immediately af
20 matches
Mail list logo
