Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: History corruption (over NFS)
- X-seq: zsh-users 8496
- From: Wayne Davison <wayned@xxxxxxxxxxxxxxxxxxxxx>
- To: Seth Kurtzberg <seth@xxxxxxx>
- Subject: Re: History corruption (over NFS)
- Date: Mon, 14 Feb 2005 14:33:52 -0800
- Cc: zsh-users@xxxxxxxxxx
- In-reply-to: <421112C4.50002@xxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20050210165417.GG30487@xxxxxxxxxxxxx> <1050210184111.ZM22490@xxxxxxxxxxxxxxxxxxxxxxx> <20050214155630.GB6395@xxxxxxxxxxxxx> <20050214185705.GC6444@xxxxxxxxx> <421112C4.50002@xxxxxxx>
On Mon, Feb 14, 2005 at 02:06:12PM -0700, Seth Kurtzberg wrote:
> Won't this cause problems in the mode where history is shared, and
> history is written for every command
Nope -- appended history still appends just fine. As mentioned, zsh
re-opens the history file for every append, so it matters not if the
file gets rewritten to a new inode. Also, every append and every
rewrite is locked by using a .zhistory.LOCK file, so multiple shells
don't update the history file at the same time.
> not just once when the shell terminates?
Zsh also periodically rewrites the history file when the number of
appended lines exceeds the SAVEHIST count by a certain percentage.
..wayne..
Messages sorted by:
Reverse Date,
Date,
Thread,
Author