1 Mar 2003 02:29
Semantics for Unix Domain bind(2)
Mike Neuman <fullyarticulate <at> yahoo.com>
2003-03-01 01:29:27 GMT
2003-03-01 01:29:27 GMT
Can anyone explain to me why the Unix Domain bind(2) requires the socket not exist on the filesystem? There are comments in the source and manual which would seem to indicate someone else thinks this is a bug as well. (See kern/uipc_usrreq.c, line 421 (OBSD32), or the man page for bind). The fix is pretty simple (about 15 lines hacked in--if we reworked the function to not do an NDINIT(,CREATE,...) first, it would likely be less), and doesn't really break anything, but it does allow the use of unix domain sockets on read-only filesystems. Is there any interest in this? -Mike Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/
RSS Feed