Citeren Giovanni Bechis <giovanni@paclan.it>:
> Hi,
> I have setup a clamav server listening on 0.0.0.0:3310 and a client
> that runs "clamdscan --no-summary --infected --stream --fdpass
> $FILE" to remotely scan files/emails for viruses.
> When clamdscan exits and the report is printed on the screen the
> connection on clamav server is kept in TIME-WAIT state for ~60
> seconds as if the connection would not be correctly closed by the
> client.
No.
> Any hints about what could keep the connection in TIME-WAIT state ?
https://en.wikipedia.org/wiki/Transmission_Control_Protocol
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
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
> Hi,
> I have setup a clamav server listening on 0.0.0.0:3310 and a client
> that runs "clamdscan --no-summary --infected --stream --fdpass
> $FILE" to remotely scan files/emails for viruses.
> When clamdscan exits and the report is printed on the screen the
> connection on clamav server is kept in TIME-WAIT state for ~60
> seconds as if the connection would not be correctly closed by the
> client.
No.
> Any hints about what could keep the connection in TIME-WAIT state ?
https://en.wikipedia.org/wiki/Transmission_Control_Protocol
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
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