Re: [zsh 3.1.9] history bug?

[Matt Armstrong <matt.armstrong@xxxxxxxxxxxx>]

On Wed, Nov 29, 2000 at 10:01:34PM +0200, Mircea Damian wrote:
> I'm seeing a problem with history too. Ok. It saves history but if for any
> reason (like kill -9 when it's saving history) the file .history.LOCK
> remains and a process with the pid of zsh is running I will not be able to
> login (/bin/zsh is my default shell).
> 
> For example I do a shutdown, the system is very busy and zsh receives
> SIGHUP from shutdown, it starts to write the history (creates to lock) but
> the shutdown sends (after a while) SIGKILL and it doesn't finish (the .LOCK
> remains) the system reboots.. and voila I'm not able to login because
> sendmail is running with the same PID that zsh had.
> 
> Is that ok?
> 
> (I have here Linux with glibc-2.1.3 and zsh-3.1.9)
> 
> PS: Should I try 3.1.9-dev-7?

It looks like 3.1.9-dev6 will kill the lockfile if it isn't available
for 10 seconds.  So 3.1.9-dev-7 probably fixes your problem.