On Sun, Oct 12, 2014 at 4:54 PM, Richard Laager <rlaa...@wiktel.com> wrote:
> On Sun, 2014-10-12 at 14:18 -0500, Cliff Hayes wrote:
>> I tried your idea.
>> I updated the following in clamd.conf:
>> LocalSocket /var/run/clamav/clamd.socket
>> PidFile /var/run/clamav/clamd.pid
>> User clamav
>>
>> Now I get this error when starting clamd:
>> ERROR: Can't open/parse the config file /usr/local/etc/clamd.conf
>> I am starting as root as instructed in clamd.conf
>> I have gotten that error before ... it usually means there is a user
>> issue. When I go back to running as root it knows to look in /etc/ for
>> clamd.conf
>
> I have no idea why your clamd is looking in /usr/local/etc instead
> of /etc.
There are probably 2 or more different version of clamd on this
system, built with different default options. If packages have been
installed from different 3rd party repositories or installed from
source plus a packaged install, that is a likely scenario.
--
Les Mikesell
lesmikes...@gmail.com
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
