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

Re: History file corruption on NFS

X-seq: zsh-workers 26222
From: Vincent Lefevre <vincent@xxxxxxxxxx>
To: Richard Hartmann <richih.mailinglist@xxxxxxxxx>
Subject: Re: History file corruption on NFS
Date: Thu, 1 Jan 2009 05:19:54 +0100
Cc: 412875@xxxxxxxxxxxxxxx, Zsh Workers <zsh-workers@xxxxxxxxxx>
In-reply-to: <2d460de70812310758r5985578clcedbe11a4fb8a630@xxxxxxxxxxxxxx>
Mail-followup-to: Richard Hartmann <richih.mailinglist@xxxxxxxxx>, 412875@xxxxxxxxxxxxxxx, Zsh Workers <zsh-workers@xxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <2d460de70812310758r5985578clcedbe11a4fb8a630@xxxxxxxxxxxxxx>

On 2008-12-31 16:58:18 +0100, Richard Hartmann wrote:
> in your bug report[1] about zsh using the wrong kind of lock
> in lockhistfile, you mentioned wanting to look into the
> issue. Did you have time to do that?

The problem has been fixed upstream. See the following thread:

  http://www.zsh.org/mla/workers/2008/msg00479.html

Wayne Davison wrote a simpler patch, which was included in zsh on
2008-05-04, after version 4.3.6. It works in practice and I've also
just re-checked the code. AFAIK, this patch hasn't been backported
to Debian's package (I didn't see a HIST_FCNTL_LOCK option in the
package version 4.3.6-7). So, the Debian bug should remain open.

-- 
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)

Follow-Ups:
- Re: History file corruption on NFS
  - From: Richard Hartmann

References:
- History file corruption on NFS
  - From: Richard Hartmann

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