* Sockets and open()
@ 2003-04-07 3:11 Fredrik Tolf
0 siblings, 0 replies; only message in thread
From: Fredrik Tolf @ 2003-04-07 3:11 UTC (permalink / raw)
To: linux-kernel
Hi everyone!
This is an issue that I can hardly believe that I haven't found any references
for outside of here; it should be fundemental enough. I have searched far and
wide, without being able to find anything at all. If you know of any
references, please point me to them, so that I know where they have been
hiding from me all this time.
Anyway, here it comes: How comes you can't use an ordinary open() call to
connect to a UNIX domain socket? Although I haven't been able to afford the
POSIX standard, that would seem like the natural behaviour to me. If memory
serves me, the manpage for open on OpenBSD even suggests such a behaviour
(although it is "currently not supported"), right? Nontheless, it apparently
returns ENXIO under Linux. Is this _really_ the correct behaviour? It seems
so strange to me, although I can't believe that it hasn't been implemented
because it's too hard or something like that.
It would be so immensely practical to be able to open() UNIX sockets. Is it
some kind of security consideration that I fail to see?
Thank you in advance,
Fredrik Tolf
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-04-07 3:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-07 3:11 Sockets and open() Fredrik Tolf
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®