[clamav-users] Error: define server type (local and/or TCP). but LocalSocket is set

[Scott Horton]

>> [...snip...] I surmise from this that while I had clamd running 
>> without error, it was apparently starting up with defaults and not 
>> using my config file.
>
>I didn't see a question in all that,

Apologies I wasn't clearer.  I meant the question to be:  How can I fix this
error??:

Jul 21 22:23:08 tn4 clamd: ERROR: Please define server type (local and/or
TCP).
Jul 21 22:23:08 tn4 systemd: clamd at amavisd.service: main process exited,
code=exited, status=1/FAILURE Jul 21 22:23:08 tn4 systemd: Unit
clamd at amavisd.service entered failed state.
Jul 21 22:23:08 tn4 systemd: clamd at amavisd.service failed.

>I assume you're restarting daemons after changing their configuration 
>files, many won't reread them without being restarted or e.g. sigHUPed.

Yes, even rebooting in desperation sometimes.


> I wonder if you're trying to
>use a volatile filesystem (/tmp to hold sockets) before the OS startup 
>scripts have created it.

The sockets settings I have are in these files /etc/clamd.d/amavisd.conf
/etc/clamd.conf  (link to below) /etc/clamd.d/scan.conf All have:
	LocalSocket /var/run/clamd.amavisd/clamd.sock
	
/etc/amavisd/amavisd.conf
Has:
    \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamd.amavisd/clamd.sock"],

/var/run is linked from /run on this box.  I don't know if that's volatile
or not.


Thanks, Scott