Yes, thanks, but I'm already using TCPSocket for this purpose -- without
Containers.
My question is whether a file descriptor passed via a socket is valid
in a different container than where it was created. I can easily see the
kernel rejecting it as a security violation, maybe unless some option
Hi there,
On Sat, 23 Jul 2016, Paul Kosinski wrote:
... Could this be made to work if clamd were running in a different
Linux container?
Yes.
man clamd.conf
Look for 'TCPSocket'.
--
73,
Ged.
___
Help us build a comprehensive ClamAV guide:
https:
I couldn't find anything in some quick Google searches about this, and I
don't remember seeing anything relevant on this list, so I will ask:
Currently I avoid clamscan startup delay on ad-hoc scans by using a
small Perl script to expand the name(s) of the file(s) or directory(s)
to be scanned and
