Thank you very much for taking the time to respond. It is truly appreciated...
I was able to make your suggestion work by removing the following two lines from clamd.conf: User clamav LocalSocketGroup simscan which creates the socket thusly: srw-rw---- 1 root root 0 Jul 31 10:04 clamd.socket This way clamd runs as root, daemontools can restart clamd, and simscan can scan the test message. It works, but I am not really liking the idea of running clamd as root. Seems to me that that has as many risk variables as giving world perms to a non-root process (which didn't really work as expected anyway). So is this to say that it is not possible to run clamav under a non-root user if you want to grant group access to the socket? I can see/understand why using root works (and thank you again for showing it to me), but I still fail to understand the cause behind my previous observations that group permissions do not seem to work on the socket? -- Computerisms Bob Miller 867-334-7117 / 867-633-3760 http://computerisms.ca On Wed, 2013-07-31 at 11:38 +0100, G.W. Haywood wrote: > Hi there, > > On Wed, 31 Jul 2013, Bob Miller wrote: > > > Thanks for any thoughts you wish to share... > > Set the owner of the socket to root, and then repeat your tests. > > -- > > 73, > Ged. > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://www.clamav.net/support/ml _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
