Subject: kern/6062: bind() to unix domain socket doesn't use emul path
To: None <gnats-bugs@gnats.netbsd.org>
From: None <sp128@ibm.net>
List: netbsd-bugs
Date: 08/27/1998 23:55:58
>Number: 6062
>Category: kern
>Synopsis: bind() to unix domain socket doesn't use emul path
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: kern-bug-people (Kernel Bug People)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Aug 27 23:05:00 1998
>Last-Modified:
>Originator: Steve Peurifoy
>Organization:
>Release: 1.3
>Environment:
System: NetBSD loop 1.3 NetBSD 1.3 (axel) #8: Wed Apr 29 21:45:19 MDT 1998 root@loop:/usr/obj/sys/arch/hp300/compile/axel hp300
>Description:
When bind() attaches a path name to a unix domain socket, an applicable
emulation path is not used in determining where to create the filesystem
node.
>How-To-Repeat:
Although this was discovered in an HP-UX emulation environment, I
believe the problem is MI. If the HP-UX X server is run under emulation
its listen socket will be created in /usr/spool/sockets/X11 rather than
/emul/hpux/usr/spool/sockets/X11. Looking at the code for sys_bind()
and unp_bind() makes me believe that other OS emulations will do the same.
>Fix:
>Audit-Trail:
>Unformatted: