I'll keep this short since I'm not sure that I have permission to
post yet. I'm getting the digest, but being told my postings here
are not allowed. According to what I understood from the various
instructions and nag messages, I must subscribe first to the digest
and that then allows me to post he
Dennis Peterson wrote:
> It might be that you still have an earlier version of clamscan on your
> system and this can be found by running "which clamscan" if you're using
> Linux or Unix.
Thanks to all and you, Dennis in particular.
Here are the results in Fedora Core kernel 2.6.12-1.1376_FC3
G.W.,
Hi, thanks for the insights:
> [901 lines of garbage about top-posting trimmed - I'm on the digest.]
Amen. I'm on the newsgroup (see below), but fwiw I LIKE top posting,
I immediately know what is latest... But I digress ... The solution
is to leave the digest and use the newsgroup, detail
Jeff hi, thanks
> Ged is correct.
>
> Type
>
> # which clamscan
>
> at your shell prompt and it will tell you where in your $PATH it is
> finding the executable.
This returns:
[EMAIL PROTECTED] services]# which clamscan
/usr/local/bin/clamscan
So the installation is indeed th
Dennis hi
> The real point of education is that these duplicate files can and do exist
> and that a good clean uninstall is needed for a good clean install.
I agree. I'll report back tomorrow, but it looks like the old
freshclam.log was generating the issue with clam-update.
I've now nuked all o
Fajar hi, thanks.
> My guess is you have both /usr/bin/clamscan ( from RPM) and
> /usr/local/bin/clamscan (from manual build). The same goes for libs also.
. You are correct, thanks:
/usr/bin/ contains May 18, 2005 versions of
clamav-config
clamdscan
clamscan
C. Andrews Lavarre wrote:
> I agree. I'll report back tomorrow, but it looks like the old
> freshclam.log was generating the issue with clam-update.
>
> I've now nuked all older versions of freshclam and clamscan, cleaned
> out the freshclam.log of older entries, still h
Bob Hutchinson wrote:
> try
> ps ax | grep freshclam
Oooh. Very good:
[EMAIL PROTECTED] clamav-0.87.1]# ps ax | grep freshclam
5220 ?Ss 0:00 /usr/bin/freshclam -d -p
/var/run/clamav/freshclam.pid
> if it's there, try and figure out what is starting it (if you haven't
