Author demian.brecht
Recipients berker.peksag, demian.brecht, flox, loewis, mcjeff, polymorphm
Date 2014-12-16.08:17:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418717857.11.0.252412734222.issue14134@psf.upfronthosting.co.za>
In-reply-to
Content
> in GNU/Linux "system timeout has been reached" -- means that  system timeout will *never* reached.

That's quite likely because the system limits may be very large. For example, on my OSX box:

    --- ~ ยป sysctl net.inet.tcp.keepinit
    net.inet.tcp.keepinit: 75000

According to Apple developer docs, this is in seconds. Meaning for your example to run all 100 iterations, you'd be looking at an inordinate amount of time to finish a loop that timed out at each connection attempt and deferred to system defaults for the timeout value. Not exactly "never", but far from a reasonable time frame. Of course, this can be tuned to a more reasonable limit.
History
Date User Action Args
2014-12-16 08:17:37demian.brechtsetrecipients: + demian.brecht, loewis, flox, mcjeff, polymorphm, berker.peksag
2014-12-16 08:17:37demian.brechtsetmessageid: <1418717857.11.0.252412734222.issue14134@psf.upfronthosting.co.za>
2014-12-16 08:17:37demian.brechtlinkissue14134 messages
2014-12-16 08:17:36demian.brechtcreate