Subject: Re: [sup-talk] error message running sup

From: Eric Sherman <[email-masked]>
Date: Thu, 10 Jun 2010 13:15:40 -0400

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
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Daniel Goldin <[email-masked]>
Date: Thu, 10 Jun 2010 10:04:45 -0700

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