[Date Prev][Date Next]
Re: Socket-level timeouts?
On Apr 8, 2008, at 7:23 PM, Dave Horsfall wrote:
On Tue, 8 Apr 2008, Aaron Richton wrote:
For that matter, I'm having a hard time envisioning the situation you
describe playing out. Let's say your server dies hard and you
Our situation was a frozen disk controller on the server; it happily
accepted connections, which never timed out...
We've had similar storage failures, and two slapd bugs: hitting the
maximum file descriptor limit (new connections were accepted but not
serviced - (http://bugs.debian.org/378261) and the bdb backend
deadlocking until we learned to set the number of locks to a value
much higher than was suggested when I first set the server up (http://bugs.debian.org/303057
This why I'm pretty big on making the client not trust the server to
operate perfectly since there are many things which can go wrong, most
of which can be addressed by a single client-side fix instead much
difficult server-side hardening.
Description: S/MIME cryptographic signature