On 12/7/12 11:44 PM, Jim Preston wrote:
On 12/06/2012 12:12 PM, Gene Heskett wrote:
On Thursday 06 December 2012 14:09:16 Dennis Peterson did opine:
On 12/6/12 10:44 AM, Gene Heskett wrote:
Speaking of clamd.conf, I wonder if some of you might be editing the
wrong clamd.conf file? I am not sure how it got to be, but according
the the launcher script in /etc/init.d. it is using
/etc/clamav/clamd.conf, but I have others also.
You should make no assumptions about the location of the clamd.conf
file. It can be anywhere but is specified by the configure/compile
operation, the installer if built from source, the RPM packager, and
the
command line in the launch script. Any or all can be screwed up or got
right by any of the people involved.
dp
Of course I understand that Dennis, but when you go from an old,
broken deb
install, to a tarball build and then back to a deb install, these
installs
have no clue that they are replacing a different install, so its best to
end the confusion and summarily nuke the old stuff.
Cheers, Gene
Yes, and one way is to do an uninstall before upgrading. I do this for
each of my clamav upgrades. I have found that each of the distro's
tends to customize the install location to their own liking and which
is usually not the same as anyone elses.
Jim
That has made it hard to find multiple sources of distros that will work
interchangeably :). And yum and rpm will not remove or replace those
packaged files that are not identical to what came from the package
which makes it worse. At best you can expect to see a .rpmnew as an
extension to duplicated files.
dp
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
