Named Pipes across NFS?

[Tim Tsai]

barmar at think.com (Barry Margolin) writes:
[lines deleted]
>pipes are implemented entirely within the local kernel (didn't Jonathan
>Kamens just answer this question a day or two ago?).

  Yes he did..  I was the one that asked the question..

>Why does it need to be a named pipe?  If the server and clients can be on
>different machines, why not just use a regular file?  Named pipes are
>simply optimizations that exist for processes on the same host.

  In my case, I have my .plan set up as a named pipe and a daemon that
searches the process table for the finger process when awaken.  This
will only catch fingerers from the local host, which was fine, but if a
NFS-mounted station tries to read my .plan, it blocks, and causes
erratic behavior with the daemon until .plan is read from the original
host.

>--
>Barry Margolin, Thinking Machines Corp.
>barmar at think.com
>{uunet,harvard}!think!barmar
--
  Never argue with a fool, people might not know the difference.
                                                       <Murphy's Law>