From: Daniel Goldin <danielgoldin@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] error message running sup
Date: Thu, 10 Jun 2010 10:04:45 -0700 [thread overview]
Message-ID: <AANLkTilOLdBrK50s_r2Kd-WqFGirhQxzWwCI9hmdlCLB@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 426 bytes --]
When I run sup-sync, I get the following message:
Error: the index is locked by another process! User '' on
host '' is running with pid.
The process was alive as of at least 54 minutes ago.
Should I ask that process to kill itself (y/n)? n
Sorry, couldn't unlock the index.
Couldn't find the process running ps -aux. Any help gratefully appreciated.
Again I am a non-programmer so go easy.
--
Daniel Goldin
626.817.2462
[-- Attachment #1.2: Type: text/html, Size: 534 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-06-10 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 17:04 Daniel Goldin [this message]
2010-06-10 17:15 ` Eric Sherman
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=AANLkTilOLdBrK50s_r2Kd-WqFGirhQxzWwCI9hmdlCLB@mail.gmail.com \
--to=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