From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-32576-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 20743 invoked by alias); 24 Apr 2014 17:59:16 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 32576
Received: (qmail 14210 invoked from network); 24 Apr 2014 17:59:00 -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=-0.9 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,T_DKIM_INVALID,
	T_TO_NO_BRKTS_FREEMAIL autolearn=no version=3.3.2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=53VWqQQwkInJF9W/H6wTJLckuxhSyQvfGtBcfLmoCxA=;
        b=E/HBAR6TE6JmRy8eWDtmvmJ4zED2XUWZ0xnyzItYKvRxHU87K5xP0k+xNxdYLmjdhR
         MyFl0zHZfsFmAfUL1XrJbtY8wCMCuIWiGaQNEjlUSPuoIHRBNJoiKHivYLP8ORmy8/Sy
         1g/y6db+DyE2YvpeI7nsio9ikP/dvWYoQgdVFw8QJZ8tOSCoDvh/9oZUWBsufJ3Wwm8T
         6j4uM/pvhbVsM+lWkIptwNpawFuW9wq6TgYkcjhQlYdE0gmDs9YTQ9L5W7ZXwn4P4mvw
         9SYPHsfo5H6l5sbBAEIHtXLrYAly2A9Wo6JJeRK7lh6voDQ/PTtyN+yfH6NkElWuwBIS
         wgsg==
X-Received: by 10.112.87.226 with SMTP id bb2mr1976281lbb.29.1398362333710;
        Thu, 24 Apr 2014 10:58:53 -0700 (PDT)
X-Google-Original-From: Andreas <klingt.net@googlemail.com>
Message-ID: <535950DB.3060506@googlemail.com>
Date: Thu, 24 Apr 2014 19:58:51 +0200
From: Andreas <klingt.net@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: zsh-workers@zsh.org
Subject: Re: Re: zsh got stuck without any message because of history lock
 file
References: <53594068.4040503@googlemail.com>
In-Reply-To: <53594068.4040503@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On Thu, 24 Apr 2014 10:02:28, Bart wrote:
> ... 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.

I deleted the file already, but i remember that the timestamp was in the future, maybe the system crash got the file to be corrupt.

Andreas