Andreas Aardal Hanssen wrote:
Well, the logs clearly show that 60 seconds of idle later binc times out the connection. Although it has seemed that it doesn't close the TCP connection, because usually later the same process shows a failure of authentication and then the client closes the connection.
Are you sure you're not mixing the idle timeout with the auth timeout, which has a default of 60 seconds?
Well, binc wouldn't tell me 'closing connection, idle for 60 seconds' if it was the auth timeout, right? :)
The auth timeout seems to happen 60 seconds after the idle timeout. Although still on the same connection.
--Kurt
