On Tue, 20 May 2003, David Vasil wrote:
> On Tue, May 20, 2003 at 03:22:15PM -0500, [EMAIL PROTECTED] wrote:
> > > On Tue, May 20, 2003 at 02:54:36PM -0500, [EMAIL PROTECTED] wrote:
> > > > yes not found in the data directory.
> > > > yes not found in the data directory.
> > > > ERROR: yes not found on remote server
> > > > ERROR: Can't download yes from clamav.elektrapro.com
>
> After looking at the source code for freshclam.c and manager.c
> in the ${CLAMSOURCEDIR}/freshclam directory it looks like 'yes'
> is actually a #DEFINE for the database names (in this case,
> DB1NAME and DB2NAME).
>
> The database names should be defined in the makefile with these
> flags: -DDB1NAME=\"viruses.db\" -DDB2NAME=\"viruses.db2\"
>
> How did you run your configure script? Check your Makefile in
> the freshclam directory and see what the DEFS line shows. What
> are DB1NAME and DB2NAME set to? I think this should fix your
> problem.
I configured it with...
./configure --prefix=/usr/local --sysconfdir=/etc/clamav
--localstatedir=/var --disable-clamuko --with-db1 --with-db
I left the name of db1 and db2 blank which typically makes most configure
scripts insert a default filename or path. I reconfigured it with
--with-db1=viruses.db --with-db2=viruses.db2
I reran freshclam and the output changed to this:
Checking for a new database - started at Tue May 20 15:59:22 2003
Current working dir is /usr/local/share/clamav
yes not found in the data directory.
yes not found in the data directory.
Connected to clamav.elektrapro.com.
Reading md5 sum (viruses.md5): OK
Reading md5 sum (viruses2.md5): OK
ERROR: yes not found on remote server
ERROR: Can't download yes from clamav.elektrapro.com
Interesting. So it's now checking the md5sums but it still can't find
"yes".
Ah ha! If you don't provide a filename at all it uses the following in
DEFS:
-DDB1NAME=\"yes\" -DDB2NAME=\"yes\"
That explains it. It would appear in fact that you don't need to specify
--with-db1 or --with-db2 at all unless you want to change the filenames.
By not using them with configure it still creates the appropriate DEFS
line. It looks like the only way you can go wrong here is if you don't
define the filename.
Well, that seems to have fixed my problem. Thanks for pointing me in the
right direction.
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
