Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: fifo configure check
- X-seq: zsh-workers 2575
- From: Zefram <zefram@xxxxxxxxxxxxxxxxx>
- To: schaefer@xxxxxxx
- Subject: Re: fifo configure check
- Date: Fri, 13 Dec 1996 14:44:37 +0000 (GMT)
- Cc: zsh-workers@xxxxxxxxxxxxxxx
- In-reply-to: <961212193711.ZM6210@xxxxxxxxxxxxxxxxxxxxxxx> from "Bart Schaefer" at Dec 12, 96 07:37:11 pm
Bart wrote:
>On Dec 13, 3:30am, Zoltan Hidvegi wrote:
>} Subject: fifo configure check
>}
>} I discovered that fifo test fails if zsh is compiled in an NFS mounted
>} directory.
It works for me on NFS-mounted filesystems. (Solaris 2.5.1 and SunOS
4.1.4.) If FIFOs don't work on such filesystems, then that is a
serious bug in the operating system.
>} The patch below shoud fix it (it's only for configure.in, you
>} need autoconf). I did not test it but it should work.
It is certainly sensible to perform the test on the same filesystem we
will actually use the FIFOs on. But the fixed name in /tmp can cause
clashes if two people are configuring zsh at the same time. I think
some attempt at a unique name is necessary.
>I'm concerned that fifos won't work on the ramdisk file system that many
>newer suns are configured to use for /tmp. (I know things like lockf()
>fail on the ramdisk.) Can someone who has a ramdisk /tmp please try this
>soon and let us know?
It works on Solaris 2.5.1. But of course we have /dev/fd, so the FIFOs
aren't required in any case.
-zefram
Messages sorted by:
Reverse Date,
Date,
Thread,
Author