Re: corrupt history file on NFS

[Vincent Lefevre <vincent@xxxxxxxxxx>]

On 2007-01-15 19:00:43 -0800, Bart Schaefer wrote:
> This suggests that we might be able to work around it by always having
> zsh seek to one btye short of the file size, and then read that byte,
> before it attempts to append anything to the file.

If you have a patch, I can test it to make sure this solves the problem.

> However, it's really not zsh's fault: NFS writes are not required to
> be atomic, and zsh does not know the file isn't local. So this would
> have to be controlled by an option, or something, so as not to
> penalize cases that don't need NFS "safety".

An option would be OK for me, but would this really penalize cases
with local files in practice?

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