On Monday 19 April 2004 6:50 pm, Todd Lyons wrote:
> Same problem many people are having. Your freshclam is probably
> downloading to a place that your commandline scanner knows to look, but
> your daemon is looking somewhere else.
>
> Personally I'm wondering if it would be better to remove the option to
> compile in a default location and make it require a config file
> instead. Just idle thoughts...
My feeling is that a default location is perfectly okay, provided everything
is consistent. So long as freshclam, clamscan and clamdscan all want the
signature database to be in the same place, it doesn't matter whether that
place is a default or user-defined.
The thing which needs to be avoided is (one of) the scanning tools looking for
the database in one place, and freshclam updating it somewhere else.
Surely it can't be too difficult to make sure that building the system results
in all three using a single location (no matter whether that location is a
default or not), so that someone has to start getting obscure in order to
create a discrepancy?
Regards,
Antony.
--
If you can't find an Open Source solution for it, then it isn't a real
problem.
Please reply to the list;
please don't CC me.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
