From: Eric Sherman <hyperbolist@gmail.com>
To: Daniel Goldin <danielgoldin@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] error message running sup
Date: Thu, 10 Jun 2010 13:15:40 -0400 [thread overview]
Message-ID: <1276189944-sup-3195@changeling.local> (raw)
In-Reply-To: <AANLkTilOLdBrK50s_r2Kd-WqFGirhQxzWwCI9hmdlCLB@mail.gmail.com>
Excerpts from Daniel Goldin's message of Thu Jun 10 13:04:45 -0400 2010:
> When I run sup-sync, I get the following message:
>
> Error: the index is locked by another process! User '' on
This usually means that sup was killed unnaturally and left the lockfile
laying around. Sup is reluctant to start multiple instances of itself. In
this case, since you've confirmed that another sup instance isn't running,
I believe you can safely answer "y" to this question and the one that will
follow it to start sup.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-06-10 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 17:04 Daniel Goldin
2010-06-10 17:15 ` Eric Sherman [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=1276189944-sup-3195@changeling.local \
--to=hyperbolist@gmail.com \
--cc=danielgoldin@gmail.com \
--cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox