Paul Kosinski
2016-07-22 18:12:32 UTC
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 then use clamdscan to pass file descriptor(s) to a
running (on its own userid) clamd. Could this be made to work if clamd
were running in a different Linux container?
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
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 then use clamdscan to pass file descriptor(s) to a
running (on its own userid) clamd. Could this be made to work if clamd
were running in a different Linux container?
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml