Re: unix socket & fcntl => kernel oops ?

From: Miquel van Smoorenburg (miquels@cistron.nl)
Date: Tue May 30 2000 - 17:25:07 EST


In article <cistron.20000531090240.A257@metastasis.f00f.org>,
Chris Wedgwood <cw@f00f.org> wrote:
>On Sun, May 28, 2000 at 01:46:01PM +0400, Khimenko Victor wrote:
>
> So it's not just me. Is it known issue ? Even if locking on unix
> sockets is not supported (why?) kernel oops and segmentation
> fault does not look like right rection to me :-/
>
>Open should fail on unix sockets. Does this fix your problem?

Wouldn't it be a lot more elegant if open() on a Unix socket
was equivalent to socket() / connect() ?

That would mean that server apps that now use a named pipe (fifo)
for their clients to connect to could move to a Unix socket without
changing the client at all, but they would be able to get at
the client credentials using SO_CRED

Yes I have such an app ;)

Mike.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:25 EST