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 cannot be changed on app level. Of course you can imagine i had never waited for such a long time so i suspected a bug but in fact there was none. Probably the settings on a BSD machine are different (i don't have in installed anymore) so it behaved as i expected, i couldn't say. In what concerns the POLLHUP it was again my misunderstanding as this is a return code send only when the connection is actually acknowledged as down (which as stated above can take a lot of time) . If the other side just terminates ,reading from the socket is actually possible and returns EOF ( 0 ) characters. This discussion probably belongs to a programming forum but as i brought it up i thought i would end it at least with an explanation. -- sockets SIGPIPE not sent https://bugs.launchpad.net/bugs/153649 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
