From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23010 invoked from network); 25 Mar 2002 19:45:37 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 25 Mar 2002 19:45:37 -0000 Received: (qmail 13926 invoked by alias); 25 Mar 2002 19:45:28 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16901 Received: (qmail 13915 invoked from network); 25 Mar 2002 19:45:25 -0000 Date: Mon, 25 Mar 2002 11:44:56 -0800 (PST) From: Bart Schaefer Sender: schaefer@ns1.sodaware.com To: Adam Spiers cc: zsh-workers@sunsite.dk Subject: Re: C02cond.ztst failure: -N In-Reply-To: <20020325181529.A16656@corelli.new.ox.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 25 Mar 2002, Adam Spiers wrote: > > } Could this be because the compile is happening on an NFS-mounted > > } drive? > > > > Yes, that's a very likely cause. > > In that case, would it be worth adding a check and skipping the test > when appropriate? We discussed that but I don't think anybody came up with a good test for whether the directory is NFS mounted. > Or, if that's not easily done in a portable fashion, maybe it's worth > adding a "This test might fail" type of message? Sure. In fact, all the tests involving the "newnewnew" file can fail if the clock on the NFS server is out of sync with the local clock by even a few seconds.