In message <[EMAIL PROTECTED]> Nigel Horne
<[EMAIL PROTECTED]> wrote:
>DevilsPGD wrote:
>
>>> I've created a port of clamAV for Windows, to be built and compiled
>>> using VS 2005.
>>
>> And it's amazingly fast. I ditched my cygwin implementation almost
>> instantly (well, after about four hours of testing)
>>
>> A few things... All very minor.
>>
>> 1) I can't get clamd to run under AppToService, although if I run a
>> "cmd.exe /c clamd" it works. Not a big deal.
>
>The Power Tools from www.bandsman.co.uk/clamav.htm allow you to run
>clamd as a Windows service (only tested on Windows XP Pro).
Yeah, I realize that -- I'm just pointing out that AppToService doesn't
run, which is odd -- This is the first program I've ever had to use the
"cmd.exe /c" workaround.
>> 2) clamd's selfcheck always reports a new DB, even when freshclam hasn't
>> found anything new. I have freshclam notifying clamd successfully, so
>> this check should never find anything new. I shorted the interval and
>> it still reports a new DB each time, even though freshclam last updated
>> around 4am (my time zone)
>
>I believe clamd is at fault, my hunch is that clamd just looks at
>timestamps rather than file contents. It may be best to remove all the
>contents of C:\Program Files\clamAV\data and rerun freshclam. Does that
>help?
I tried that, it didn't make a difference -- freshclam reported the
update, but the following two selfchecks (which is all I checked for)
reported the reload.
>> 3) What's the correct way to specify paths in the conf files? Since the
>> default installation is at "C:\Program Files\clamd" I decided to stick
>> with that, but when I attempt to enter that into a conf file, it gives
>> me "C:\Program" -- I've tried with and without quotes.
>>
>> C:\Progra~1 seems to work, but I wouldn't rely on that as there is no
>> guarantee that all systems will use ~1
>
>You can't enter the location of a configuration file in that file
>itself. Think about it - it's a paradox. You need to give the
>configuration file's location as an argument to clamd, thus to use
>the D drive try:
> clamd -c "D:\Program Files\clamAV\conf\clamd.conf"
No, I understand that -- But if nothing else, freshclam.conf's
notifyclam directive needs the path\filename of the clamd.conf file as
the default is not set.
>There is a known limitation in clamd.conf (and freshclam.conf) that you
>can't specify spaces in pathnames, e.g. to change the location of the
>log files. This is true of all operating systems, since it is a clamd
>issue rather than an issue on the Windows version. You can raise the
>issue either by discussing it on the clamav-users mailing list, or by
>raising a bug at [EMAIL PROTECTED]
Ahh, interesting thanks, I'll post there. Perhaps until that bug is
resolved, a different default installation path would be appropriate?
As much as I'm loath to suggest installing at %systemdrive%\clamav\ that
would seem to be more reliable.
--
Dave Warren,
MSN Instant Messenger: [EMAIL PROTECTED]
Phone: (204) 480-8407 Toll free: (888) 371-3470
Fax: (204) 283-6028
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
