I'm confused about this one. I always thought supporting open()
on Unix domain sockets would be a great idea -- there is a number
of things that you can do elegantly that way which you otherwise
wouldn't be able to do. What is wrong with it?
It's non-portable and the locking code exploded on such FDs at
present. I would suggest we leave the fix I present as is until 2.5.x
and then consider putting in non-portable semantics with a proper fix
in the posix locking code.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:11 EST