|
|You probably have 2 versions of the database. Happened to me
I finally figured that out when I tried doing sigtool --unpack-current and
it prepended the directory it was using to my entry.
|and many others. Simple to rectify: search for main.cvd on
|your box. Then find which one is being u
It would be nice if clamscan, clamd, freshclam, sigtool, etc printed out
the full path of the database files they are using (maybe only if -v is
specified?). That would help people track down what's happening.
--Eric
--
Eric Wieling * BTEL Consulting * 504-899-1387 x2111
"In a related
Colin A. Bartlett wrote:
Lynn Duerksen Sent: Wednesday, May 05, 2004 11:26 AM
Freshclam reports:
RELAY:root>[sbin] freshclam
ClamAV update process started at Wed May 5 10:07:25 2004
Reading CVD header (main.cvd): OK
main.cvd is up to date (version: 22, sigs: 20229, f-level: 1, builder:
tk
Lynn Duerksen Sent: Wednesday, May 05, 2004 11:26 AM
> Freshclam reports:
>
> RELAY:root>[sbin] freshclam
> ClamAV update process started at Wed May 5 10:07:25 2004
> Reading CVD header (main.cvd): OK
> main.cvd is up to date (version: 22, sigs: 20229, f-level: 1, builder:
> tkojm)
> Reading CVD
On Wed, 5 May 2004 10:26:16 -0500, "Lynn Duerksen" <[EMAIL PROTECTED]>
wrote:
>Freshclam reports:
>
>RELAY:root>[sbin] freshclam
>ClamAV update process started at Wed May 5 10:07:25 2004
>Reading CVD header (main.cvd): OK
>main.cvd is up to date (version: 22, sigs: 20229, f-level: 1, builder:
>t
|Subject: [Clamav-users] Sasser Worm Virus not shown with sigtool
|
|Freshclam reports:
|
|RELAY:root>[sbin] freshclam
|ClamAV update process started at Wed May 5 10:07:25 2004
|Reading CVD header (main.cvd): OK main.cvd is up to date
|(version: 22, sigs: 20229, f-level: 1, builder:
|tk
Freshclam reports:
RELAY:root>[sbin] freshclam
ClamAV update process started at Wed May 5 10:07:25 2004
Reading CVD header (main.cvd): OK
main.cvd is up to date (version: 22, sigs: 20229, f-level: 1, builder:
tkojm)
Reading CVD header (daily.cvd): OK
daily.cvd is up to date (version: 303, sigs:
