> >> 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?
The latest version from w32.clamav.net or www.bandsman.co.uk/clamav.hmt should now support spaces in pathnames with quotes, e.g.: LogFile "C:\Program Files\clamAV\log\clamd.log" > Dave Warren, -Nigel Horne _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
