An agent or agents purporting to be Shadowfirebird said: > Anyone got any ideas how I get out of this? > > >>>> > $ sup > Error: the index is locked by another process! User '' on > host '' is running with pid . > The process was alive as of at least 4216 minutes ago. > Should I ask that process to kill itself (y/n)? n > Sorry, couldn't unlock the index.
I don't have this exact problem, but I have had problems where sup has claimed to be unable to kill another instance because of a lock problem. I get a different message, but I'm running an old version. I find that sometimes Xapian has left a lockfile. If I delete .sup/xapian/flintlock then I can start sup just fine. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
