Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: corrupt history file on NFS
- X-seq: zsh-workers 23111
- From: Vincent Lefevre <vincent@xxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: corrupt history file on NFS
- Date: Tue, 16 Jan 2007 03:03:21 +0100
- In-reply-to: <20070115032716.GA22860@xxxxxxxxx>
- Mail-followup-to: zsh-workers@xxxxxxxxxx
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20070114202554.GB10583@xxxxxxxxxxxxxxxxxxx> <20070115032716.GA22860@xxxxxxxxx>
On 2007-01-14 19:27:16 -0800, Wayne Davison wrote:
> On Sun, Jan 14, 2007 at 09:25:54PM +0100, Vincent Lefevre wrote:
> > I regularly have a corrupt history file with zsh 4.3.2.
>
> Corrupt in what way?
I've done several tests, and here's more information:
* The problem occurs when I use two different machines (called courge
and doubleeagle), both x86_64.
* When a corruption occurs, there are null bytes in the history file.
* The corruption occurs almost systematically (or at least very often)
when I type a command on courge, then a command on doubleeagle. But it
*never* occurs if I read the history file with less before typing the
command. Note: the less command line isn't stored to the history file
because I either type a space first (I use histignorespace) or make
sure to recall the previous "less ..." command (I use histignoredups).
--
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)
Messages sorted by:
Reverse Date,
Date,
Thread,
Author