Re: Kernel bug with UNIX sockets not detecting other end gone?

[Olaf Titz]

> kernel does know that it has been 'disconnected'. One can even justify the
> inconcsistent behavior -- the write definitely has no place to go (now), but
> the read can't be totally sure that there is no possible way anybody could
> ever find the other end and write to it.

For a socket created with socketpair()? I'm pretty sure there is no
way for any program to find any path to it, and if there is, it's a
kernel bug. Such a socket does not have a legitimate name. (And
getsockname() reliably returns garbage, which is another bug IMHO.)

Olaf