Date: Fri, 6 Oct 2000 10:23:57 -0500 From: Dan Nelson <dnelson@emsphone.com> To: Paul Herman <pherman@frenchfries.net> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fifos over NFS Message-ID: <20001006102356.A29878@dan.emsphone.com> In-Reply-To: <Pine.BSF.4.21.0010061533360.282-100000@bagabeedaboo.security.at12.de>; from "Paul Herman" on Fri Oct 6 15:39:40 GMT 2000 References: <Pine.BSF.4.21.0010061533360.282-100000@bagabeedaboo.security.at12.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Oct 06), Paul Herman said: > My take on the nfs code (in nfs_open) is that an open() on a FIFO > should return an EACCES. I have no problems with that. But when I > > NFS Server: mkfifo foo; cat < foo > NFS Client: echo "hello world" > foo > > (over an NFS mount point) the shell hangs on the client trying to > open "foo" instead of returning an error. Did I miss something like > a mount_nfs option? I think that's expected behaviour. Fifos should be usable on NFS mounts, but an active fifo is only usable for processes running on the same machine. So if you're running completely diskless, or had NFS-mounted home dirs, for example, you can still use fifos. Your example works if you run both lines on the client, or both on the server. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001006102356.A29878>