Bug#188079: close() and/or fork() misbehaving
> Since I did not modify any C code in this package at the time the bug
> appeared, the problem must lie somewhere else. Running nbd-server in
> strace shows that it accept()s the client's call, then fork()s, as it
> should. Next, when the parent does a close() of the socket acquired with
> accept(), a FIN packet is sent to the client, closing the connection,
> although the child process still has the socket open. When it tries to
> send() something through that socket, it of course gets a SIGPIPE.
> Attached, the two files that form the output of
> strace -ff -o nbd-server-trace nbd-server 1234 /export/m68k/exp-bl-dev
Why did you assign this bug to libc6 with grave severity? What is the
problem? Which version was it worked? If I can not get valid
information, I reassign this bug back to package nbd.