Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] history locking with fcntl
- X-seq: zsh-workers 24847
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: [PATCH] history locking with fcntl
- Date: Fri, 18 Apr 2008 22:23:12 -0700
- In-reply-to: <20080419023155.GB23964@xxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20080415153120.GE1223@xxxxxxxxxxxxxxxxxxx> <20080417162307.GB22594@xxxxxxxxx> <20080418005959.GB1067@xxxxxxxxxxxxxxxxxxx> <20080419023155.GB23964@xxxxxxxxx>
On Apr 18, 7:31pm, Wayne Davison wrote:
}
} On Fri, Apr 18, 2008 at 02:59:59AM +0200, Vincent Lefevre wrote:
} > If I do not set the option (which is equivalent to not using the patch),
} > then I get immediate history corruption when using two machines (well,
} > at least 64-bit ones), 100% reproducible.
}
} Cool. Then it will be easy for you to get the real error now
I don't think there is a "real error" in the sense of a -1 return from
a system call and/or an errno value. I think everything appears to
succeed as seen from the C code, but the file is corrupted anyway.
I hope (in some sense) that I turn out to be wrong.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author