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

Re: History file locking (was Re: 4.3.4-dev-4 and 4.2.6-dev-2 available)

X-seq: zsh-workers 24258
From: Vincent Lefevre <vincent@xxxxxxxxxx>
To: Zsh hackers list <zsh-workers@xxxxxxxxxx>
Subject: Re: History file locking (was Re: 4.3.4-dev-4 and 4.2.6-dev-2 available)
Date: Fri, 14 Dec 2007 19:01:27 +0100
In-reply-to: <200712141745.lBEHjlvd017945@xxxxxxxxxxxxxx>
Mail-followup-to: Zsh hackers list <zsh-workers@xxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <22582.1197372038@xxxxxxx> <20071211235807.GB10374@xxxxxxxxxxxxxxxxxxx> <200712120948.lBC9motE009939@xxxxxxxxxxxxxx> <20071214165524.GA13214@xxxxxxxxxxxxxxxxxxx> <200712141745.lBEHjlvd017945@xxxxxxxxxxxxxx>

On 2007-12-14 17:45:47 +0000, Peter Stephenson wrote:
> We can probably add your stuff as an option; I'm a bit worried about
> forcing fcntl() locking on everybody willy nilly.

A runtime option would be the best solution. On the NFS server here,
fcntl locking sometimes no longer works (probably because the lockd
daemon has crashed), though in general, the NFS server completely
crashes a few hours later. A runtime option would allow ones to work
in a degraded mode.

>  This probably needs to wait till after 4.3.5 otherwise that will
> never get out at this rate.

OK.

> It's possible there's an overagressive test for a write failure; I added
> some more after reports of problems.  You might be able to track down
> where this is coming from fairly easily.

I'll try to look at it.

-- 
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 / Arenaire project (LIP, ENS-Lyon)

References:
- History file locking (was Re: 4.3.4-dev-4 and 4.2.6-dev-2 available)
  - From: Peter Stephenson

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