Hi there, On Sat, 26 Nov 2022, Jorge Elissalde via clamav-users wrote:
... I cannot send CONTSCAN command using IDSESSION. After scanning the file using CONTSCAN command clamd closes the socket. The same happens for any command not using IDSESSION.
That's correct.
Why does clamd closes the socket?
It's tidier than leaving it open and doing nothing with it. I don't remember anyone asking this question before. AFAIK it's always been this way.
Is there another way to do that?
I'm not sure that I understand the question. Is it a problem to open a connection to clamd?
Changing clamd.conf is not a solution, I need both options available (archives scanning and not archives scanning).
Sometimes I run several copies of clamd, all using different configs and of course listening to different sockets. Might that be an option for you? -- 73, Ged. _______________________________________________ Manage your clamav-users mailing list subscription / unsubscribe: https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
