Julio Maidanik said:
>
> Dennis Peterson wrote:
>>
>> Ok - so here's what I did. Configured clamd to use a Unix socket. This
>> requires you disable the TCP socket option - can't have both. Wrote a
>> perl tool that connects to that socket and sends it the location of a
>> file I wish to scan. Work
Dennis Peterson wrote:
>
> Ok - so here's what I did. Configured clamd to use a Unix socket. This
> requires you disable the TCP socket option - can't have both. Wrote a
> perl tool that connects to that socket and sends it the location of a
> file I wish to scan. Works great, fast, efficient, etc
Julio Maidanik said:
>
>
> Dennis Peterson wrote:
>> Stephen Gran said:
>>> On Thu, Aug 18, 2005 at 04:00:19PM +0200, Marc Haber said:
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
>>
Julio Maidanik said:
>
> I believe you are wrong: clamd socket, when specified in clamd.conf is
> for
> control only.
> When a client, like clamdscan wants to pass data to clamd uses either a
> temporary file or a socket (in case clamdscan input is stdin).
> At least, that is what I conclude from
Dennis Peterson wrote:
> Stephen Gran said:
>> On Thu, Aug 18, 2005 at 04:00:19PM +0200, Marc Haber said:
>>> 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.
Stephen Gran said:
> On Thu, Aug 18, 2005 at 04:00:19PM +0200, Marc Haber said:
>> 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 comman
On Thu, Aug 18, 2005 at 04:00:19PM +0200, Marc Haber said:
> 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
> I honestly expected the VERSION command to query memory instead of
> triggering a read of the files on disk. But then again, I can see where
> a read of memory could be wrong since (IIRC) a RELOAD doesn't actually
> perform the reload until the next new message comes in. Is that still
> the cas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Gran wanted us to know:
>> However, the VERSION command and clamdscan -V report the new database
>> version immediately after putting the new databases in place.
>Both do indeed scan the on disk databases for version information.
Verified her
On Fri, Aug 19, 2005 at 05:13:25PM +0100, Brian Morrison said:
> On Fri, 19 Aug 2005 12:07:28 -0400 in
> [EMAIL PROTECTED] Stephen Gran <[EMAIL PROTECTED]>
> wrote:
>
> > clamdscan has no real way of knowing what the daemon is using, so
> > having it output the on disk version is the only thing
On Fri, 19 Aug 2005 12:07:28 -0400 in
[EMAIL PROTECTED] Stephen Gran <[EMAIL PROTECTED]>
wrote:
> clamdscan has no real way of knowing what the daemon is using, so
> having it output the on disk version is the only thing that makes
> sense. I suppose it could be reimplemented so that clamdscan
On Thu, Aug 18, 2005 at 04:00:19PM +0200, Marc Haber said:
> 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.
Or set SelfCheck in clamd.conf, but yes, the general idea
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 after putting the new databases in p
13 matches
Mail list logo
