From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9784 invoked by alias); 24 Apr 2014 17:03:19 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32575 Received: (qmail 13857 invoked from network); 24 Apr 2014 17:02:53 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140424100228.ZM10689@torch.brasslantern.com> Date: Thu, 24 Apr 2014 10:02:28 -0700 In-reply-to: <53594068.4040503@googlemail.com> Comments: In reply to Andreas "zsh got stuck without any message because of history lock file" (Apr 24, 6:48pm) References: <53594068.4040503@googlemail.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: zsh got stuck without any message because of history lock file MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Apr 24, 6:48pm, Andreas wrote: } Subject: zsh got stuck without any message because of history lock file } } My zsh got stuck without any error message, because the } ~/.zsh-history.LOCK file wasn't deleted after a system crash. The history mechanism should time out on lock attempts after a few seconds ... oh. Was the system clock perhaps wrong, or did the crash result in a lock file with a timestamp in the future? The way the code is currently written the shell will wait until 10 seconds after the modification time stamp of the file. If for some reason the time stamp is wrong (clocks out of sync with NFS server, for example) then it may end up waiting for longer. This should get fixed.