>Number:         114
>Category:       kern
>Synopsis:       fifofs bugs/features
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb  8 09:35:02 1994
>Originator:     James Jegers
>Organization:
"	"
>Release:        
>Environment:
	
System: NetBSD na1.cs.uwm.edu 0.9a JIMJ#0 i386


>Description:
	The fifofs (named pipes in the filesystem) have some strange behavious
	which I'm not sure if they are bugs or features.

	1.  A pipe can only be open as read or as write, not as read/write.
	    I see this comparison is the first line in the fifo_open code. Other
	    machines I've worked on, AIX, HPUX, Solaris, Sun4.1 support
	    opening of the pipe for both reading/writing.

	2.  If one opens the pipe for reading, and there is not a writter at
	    the other end:  Doing a select for read will return true, but
	    when the read is actually done it will block as there really
	    isn't any data there.  This might be a because pipes are implmented
	    as sockets, maybe there should be a check in there for select
	    to see if the other end of the socket exists instead of just
	    calling the socket_select.
	
>How-To-Repeat:
	
>Fix:
	
>Audit-Trail:
>Unformatted:


------------------------------------------------------------------------------