Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: History corruption (over NFS)

X-seq: zsh-users 8498
From: Vincent Lefevre <vincent@xxxxxxxxxx>
To: zsh-users@xxxxxxxxxx
Subject: Re: History corruption (over NFS)
Date: Tue, 15 Feb 2005 10:50:30 +0100
In-reply-to: <1050214162440.ZM6002@xxxxxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: zsh-users@xxxxxxxxxx
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
References: <20050210165417.GG30487@xxxxxxxxxxxxx> <1050210184111.ZM22490@xxxxxxxxxxxxxxxxxxxxxxx> <20050214155630.GB6395@xxxxxxxxxxxxx> <1050214162440.ZM6002@xxxxxxxxxxxxxxxxxxxxxxx>

On 2005-02-14 16:24:40 +0000, Bart Schaefer wrote:
> Try changing from "noac" to an explicit "hard".

The nfs(5) man page says:

   hard       If an NFS file operation has a major timeout then report
              "server not responding"  on  the  console  and  continue
              retrying indefinitely.  This is the default.

Why would this option change anything here?

-- 
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Follow-Ups:
- Re: History corruption (over NFS)
  - From: Bart Schaefer

References:
- History corruption (over NFS)
  - From: Vincent Lefevre
- Re: History corruption (over NFS)
  - From: Bart Schaefer
- Re: History corruption (over NFS)
  - From: Vincent Lefevre
- Re: History corruption (over NFS)
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author