Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!brutus.cs.uiuc.edu!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!david
From: david@elroy.jpl.nasa.gov (David Robinson)
Newsgroups: comp.unix.questions
Subject: Re: Making a named pipe over NFS
Keywords: /etc/mknod, fifo, NFS, SunOS
Message-ID: <1989Oct11.230855.6089@elroy.jpl.nasa.gov>
Date: 11 Oct 89 23:08:55 GMT
References: <2388@munnari.oz.au>
Reply-To: david@elroy.UUCP (David Robinson)
Organization: Image Analysis Systems Grp, JPL
Lines: 31

In article <2388@munnari.oz.au> ok@cs.mu.oz.au (Richard O'Keefe) writes:
<I am using a Sun-3/50 called mudla.  Here's what /etc/motd says about it:
<SunOS Release 4.0_Export (MULLO_CLIENT_50) #1: Wed May 24 18:23:08 EST 1989
<
<My files are held on a file server called mullauna, an Encore Multimax,
<and are accessed through NFS.  Here's what I see when I log in on mullauna:
<UNIX System V Release ax.2.2f ns32332
<
<Now, SunOS supports named pipes, and System V supports named pipes, and
<the network is the computer, so named pipes should work, not so?  No.
[Description of how it fails]
<    Is this supposed to work, or should I just forget about named pipes?

Named pipes are not the the current NFS protocol (v2), but they are
supported in some NFS implementations.  In SunOS 3.2 named pipes were added
and the corresponding NFSSRC 3.2(may be off on the number), which many
vendors base their NFS on, included a kludge to handle named pipes
correctly.  Most vendors have picked this up but not all.  

It would appear that either Encore is running an NFS based on an old
version of the reference port or they built their own from scratch.
In either case it is a problem with your vendor's code.




-- 
	David Robinson		elroy!david@csvax.caltech.edu     ARPA
				david@elroy.jpl.nasa.gov	  ARPA
				{cit-vax,ames}!elroy!david	  UUCP
Disclaimer: No one listens to me anyway!