Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: History corruption (over NFS)
- X-seq: zsh-users 8493
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: History corruption (over NFS)
- Date: Mon, 14 Feb 2005 16:24:40 +0000
- In-reply-to: <20050214155630.GB6395@xxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20050210165417.GG30487@xxxxxxxxxxxxx> <1050210184111.ZM22490@xxxxxxxxxxxxxxxxxxxxxxx> <20050214155630.GB6395@xxxxxxxxxxxxx>
On Feb 14, 4:56pm, Vincent Lefevre wrote:
} Subject: Re: History corruption (over NFS)
}
} The "noac" didn't change anything (except making command execution
} slower).
}
} If I've understood correctly, the first "ssh priam" started a zsh that
} truncated the history file (since its size was above the limit). Note
} that I quit this shell immediately. Then the current zsh instances
} went on writing to the history file without noticing that it had been
} truncated, hence the null bytes.
Try changing from "noac" to an explicit "hard". I wouldn't have thought
this was needed in a modern NFS environment, but the symptoms sure look
familiar.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author