Actually this is a problem only if there is an intermediate cache.. It is not a
problem for freshclam anyways.. Sorry for the noise.
- Original Message
From: Tomasz Kojm <[EMAIL PROTECTED]>
To: clamav-users@lists.clamav.net
Sent: Tuesday, July 29, 2008 2:39:48 PM
Subject: Re: [Clamav
On 2008-07-29 16:51, Sujit Acharyya-Choudhury wrote:
> ClamAV 0.93.3/7877/Tue Jul 29 12:43:08 2008
>
> Output of clamconf is:
> # clamconf
> /etc/clamd.conf: clamd directives
> --
> LogFile not set
> LogFileUnlock = no
> LogFileMaxSize = 1048576
> LogTime = no
> LogClean
ClamAV 0.93.3/7877/Tue Jul 29 12:43:08 2008
Output of clamconf is:
# clamconf
/etc/clamd.conf: clamd directives
--
LogFile not set
LogFileUnlock = no
LogFileMaxSize = 1048576
LogTime = no
LogClean = no
LogVerbose = no
LogSyslog = yes
LogFacility = "LOG_MAIL"
PidFile = "
dig @ns2.clamav.net db.DK.clamav.net soa
is 2008072501 here, so clearly soa needs update to have ttl refreshed data
ns1.clamav.net timeout here, have not tested the rest ns records
is it all working as it should ?
--
Benny Pedersen
Need more webspace ? http://www.servage.net/?coupon=cust37098
On Tue, 29 Jul 2008 01:53:22 -0700 (PDT)
Gerald Naveen <[EMAIL PROTECTED]> wrote:
> Hi Tomasz,
>
> However, there is definitely a different issue.
>
> Freshclam uses the modification timestamp of the file from the filesystem.
> This creates a problem when the server and the client (freshclam) a
On Tue, 29 Jul 2008 01:53:22 -0700 (PDT)
Gerald Naveen <[EMAIL PROTECTED]> wrote:
> Hi Tomasz,
>
> However, there is definitely a different issue.
>
> Freshclam uses the modification timestamp of the file from the filesystem.
> This creates a problem when the server and the client (freshclam) ar
Hi Tomasz,
However, there is definitely a different issue.
Freshclam uses the modification timestamp of the file from the filesystem. This
creates a problem when the server and the client (freshclam) are in different
timezones (specially when the client is ahead in the timezone).
Isn't that tr
