On 2020-09-29 08:30, Duncan Berriman via clamav-users wrote: > Good point. I will sort it out. > > Perhaps the example conf files should use/suggest a better location.
Soonish: https://github.com/Cisco-Talos/clamav-devel/pull/132/commits/d078ea13 The main roadblock is that the service manager (systemd, OpenRC, SysV init...) needs to know about that location, too, so that it can create the parent directory and make it writable to (only) the user/group that clamd is running as. I'm only guessing, but /tmp/clamd.sock was probably chosen because it works "out of the box," by virtue of /tmp being world-writable. Of course, that's why you should NOT use it... _______________________________________________ clamav-users mailing list [email protected] https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
