Hello Jim, Thanks for the response.
>Um..clamav 0.83 uses clamd.conf, not clamav.conf. This also confused me, when i looked at the man page it indicated that since 0.80 the config file name was changed to clamd.conf, but this does not seem to be the problem as i sym-linked the existing /etc/clamav.conf to /etc/clamd.conf and the same error occurred again. This is on SuSE Ent. Server 9 and i don't know why but i think they (SuSE/Novell) compiled ClamAV and hardcoded the config file to /etc/clamav.conf. I'm not sure how to verify this but i don't know how else to explain it. The overlap was my imagination, i thought i was seeing many of the same options but i see what you mean, they are specific to each service. On Tue, 2005-04-19 at 14:44 -0400, Jim Maul wrote: > Mike Partyka wrote: > > Hello, i only just started working on ClamAV version 0.83 this morning, > > with a mail server product based on HP's Open Mail, running on a SuSE > > Ent. Server 9. > > > > I am a little confused about the two configuration > > files /etc/freshclam.conf and /etc/clamav.conf, they seem to overlap and > > contain many of the same parameters. > > > > /etc/clamav.conf is here: > > > > <SNIP> > > Um..clamav 0.83 uses clamd.conf, not clamav.conf. Unless you also have > a clamd.conf i'd imagine that this is the cause of the "unable to parse > config file" error. > > > > > > > /etc/freshclam.conf file is here: > > > > <SNIP some more> > > Im not sure what overlap you are referring to. I mean they both have a > logfile option and such, but clamd and freshclam both log, so this > really isnt overlap, its necessary unless you want them to log to the > same location. > > -Jim > _______________________________________________ > http://lurker.clamav.net/list/clamav-users.html _______________________________________________ http://lurker.clamav.net/list/clamav-users.html