On Tue, Apr 13, 2004 at 03:50:48PM -0400, Jim Maul said: > > I also have the same problem. Apparently, I have two locations > > where the updates are stored. ClamAV was using > > /usr/local/share/clamav and freshclam was storing updates in > > /var/lib/clamav. So I made clamav.conf point to /var/lib/clamav > > also. > > > > And just to make sure that nothing is using /usr/local/share/clamav > > anymore, I changed the directory name to something else. > > > > I restarted clamd, amavisd and all went ok. But when I run sigtool > > --list it tells me ERROR: Can't open directory > > /usr/local/share/clamav > > > > How can I make it point to the new location of the database files? > > And how can I make sure that my clamd is now looking at the new > > location?
sigtool and clamscan both use a hard-coded path set at compile time, unless overridden with command line options, IIRC. clamd and freshclam read their respective config files. It sounds like you have set one path at compile time, and another at run time. -- -------------------------------------------------------------------------- | Stephen Gran | <Silvrbear> Oxymorons? I saw one | | [EMAIL PROTECTED] | yesterday - the pamphlet on "Taco Bell | | http://www.lobefin.net/~steve | Nutritional Information" | --------------------------------------------------------------------------
pgp00000.pgp
Description: PGP signature
