From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.179.196 with SMTP id br4cs286377icb; Thu, 2 Dec 2010 05:18:34 -0800 (PST) Received: by 10.224.20.7 with SMTP id d7mr31352qab.178.1291295914036; Thu, 02 Dec 2010 05:18:34 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id t31si1274276qcs.12.2010.12.02.05.18.33; Thu, 02 Dec 2010 05:18:34 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 8D7D319782DC; Thu, 2 Dec 2010 08:18:33 -0500 (EST) Received: from mail-qw0-f50.google.com (mail-qw0-f50.google.com [209.85.216.50]) by rubyforge.org (Postfix) with ESMTP id D5CF51858321 for ; Thu, 2 Dec 2010 08:07:44 -0500 (EST) Received: by qwi4 with SMTP id 4so3274375qwi.23 for ; Thu, 02 Dec 2010 05:07:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=cm2nEtrBQPk3Zb8OERqoNnkaE+oZPK0tT+WA0jfoVLE=; b=BbigGeUo5NgLk1k4kojxC/avYIHJVmj/wrd0DT4XcRHWfNWGrsABf36rgwVT9XUJll +RpfRu+EHG1WFAIwqAersu2rQnIg9VygWRd5tGhTG5wOROjJGpapkJiMIrEs94JecvVa h4EZzPJ6qFE5UAhicF+Zrlfh2V2Xofj03dROI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=K7o9UPu6aRlub+Xv3V1q1nzcDW3ubia8oQ6Nmvifivg3YWWwUCrg/yVSQF7Xa3oYa3 JIpITz3tExZiZqMgb8ilBJPBfrjfnuI9X/dm5bV56EaXQJ3U4G1OZ3DmctXaXh8DOF7H rQ/9vwxxfpnWZzQ5kLF5nsw7q7yCB1fC+9EC8= MIME-Version: 1.0 Received: by 10.229.190.204 with SMTP id dj12mr30891qcb.66.1291295264282; Thu, 02 Dec 2010 05:07:44 -0800 (PST) Received: by 10.229.237.209 with HTTP; Thu, 2 Dec 2010 05:07:44 -0800 (PST) In-Reply-To: <1291294338-sup-7754@leda> References: <1291294338-sup-7754@leda> Date: Thu, 2 Dec 2010 13:07:44 +0000 Message-ID: From: Shadowfirebird To: Iain Cc: sup-talk Subject: Re: [sup-talk] Can't start Sup, allegedly because of a locked index. X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0640334778==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org --===============0640334778== Content-Type: multipart/alternative; boundary=001636164b29871af004966d1bcb --001636164b29871af004966d1bcb Content-Type: text/plain; charset=ISO-8859-1 Yes!! Thank you! On Thu, Dec 2, 2010 at 12:54 PM, Iain > wrote: > > 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. > > Something similar happened to me once. I just did "rm ~/.sup/lock", then > started sup as normal. Does that work for you? > _______________________________________________ > sup-talk mailing list > sup-talk@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-talk > -- What a tangled web we weave / Go 'round with circumstance / Someone show me how to tell / The dancer from the dance... --001636164b29871af004966d1bcb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yes!! Thank you!

On Thu, Dec 2, 2010 at 1= 2:54 PM, Iain <rhomunuq+ml_sup@gmail.com> wrote:
> Anyone got any ideas how I get out of this?
>
> >>>>
> $ sup
> Error: the index is locked by another process! User '' on
> host '' is running =A0with 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.

Something similar happened to me once. I just did "rm ~/.sup/loc= k", then
started sup as normal. Does that work for you?
_________________________________________= ______
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk



--
What a tang= led web we weave / Go 'round with circumstance / Someone show me how to= tell / The dancer from the dance...
--001636164b29871af004966d1bcb-- --===============0640334778== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk --===============0640334778==--