zsh-users
 help / color / mirror / code / Atom feed
From: Florian Bruhin <me@the-compiler.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org
Subject: Re: zsh spinning on .zsh_history.LOCK on start
Date: Wed, 11 Jun 2014 08:46:47 +0200	[thread overview]
Message-ID: <20140611064647.GT19485@lupin> (raw)
In-Reply-To: <140610234238.ZM22767@torch.brasslantern.com>

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

* Bart Schaefer <schaefer@brasslantern.com> [2014-06-10 23:42:38 -0700]:
> On Jun 11,  7:39am, Florian Bruhin wrote:
> } 
> } When I delete the lockfile, it starts up normally. After waiting some
> } while it does as well sometimes. Then the problem goes away, and some
> } weeks later magically appears again.
> } 
> } Any ideas on what's going wrong there?
> 
> If your home directory is NFS or otherwise network-mounted, make sure
> the clocks are in sync on all the hosts from which you might access it.
> 
> There is a patch in http://www.zsh.org/mla/workers/2014/msg00369.html
> (zsh-workers/32580) which is *probably* the fix for your problem.

Hmm, it's not on a NFS, but I think it's a very related problem: My
hardware clock sometimes does funny things when suspending/rebooting
(like just adjusting itself by a few minutes/hours in any direction),
so indeed that could be the issue. Some while ago my dirty workaround
of syncing via NTP when possible doesn't work anymore, and it's very
well possible these problems started appearing since then.

Thanks!

Florian

-- 
http://www.the-compiler.org | me@the-compiler.org (Mail/XMPP)
             GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2014-06-11  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  5:39 Florian Bruhin
2014-06-11  6:42 ` Bart Schaefer
2014-06-11  6:46   ` Florian Bruhin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140611064647.GT19485@lupin \
    --to=me@the-compiler.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).