Here is how it goes ; there is no bug. Lately i dug again into it and i
found the following:
The SIGPIPE was not sent because the SO_KEEPALIVE option takes by default a
huge time to become effective ( sometimes 2h or so) on a socket closed from the
other side. This is TCP level-dependent and can
i am closing this bug report then. but feel free to reopen it or file a
new bug should you get in trouble again.
** Changed in: ubuntu
Status: Incomplete => Invalid
--
sockets SIGPIPE not sent
https://bugs.launchpad.net/bugs/153649
You received this bug notification because you are a memb
Sorry , this happened so long ago... I wouldn't know what package could
be responsible with the "bug" if it is one. Truth is i should have maybe
posted it on a programming forum rather than yours,but as far as i
remember the same conditions on a bsd platform behaved ok, so this is
the only reason w
if you provide an affected package chances are mch higher someone
will have a look at this! what package would you blame?
** Changed in: ubuntu
Status: New => Incomplete
--
sockets SIGPIPE not sent
https://bugs.launchpad.net/bugs/153649
You received this bug notification because you a
