From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.134.218 with SMTP id k26cs77430bkt; Thu, 10 Jun 2010 10:27:23 -0700 (PDT) Received: by 10.231.193.209 with SMTP id dv17mr436629ibb.134.1276190842528; Thu, 10 Jun 2010 10:27:22 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 40si383890ibv.52.2010.06.10.10.27.22; Thu, 10 Jun 2010 10:27:22 -0700 (PDT) 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 BF2611858398; Thu, 10 Jun 2010 13:27:21 -0400 (EDT) Received: from mail-pz0-f199.google.com (mail-pz0-f199.google.com [209.85.222.199]) by rubyforge.org (Postfix) with ESMTP id 3D4F71858346 for ; Thu, 10 Jun 2010 13:15:48 -0400 (EDT) Received: by pzk37 with SMTP id 37so119586pzk.27 for ; Thu, 10 Jun 2010 10:15:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:cc:subject:from :to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=bZ8nOxGvtjgTu8iRLrI09I0cWMcEUMEic7csdl+qfWQ=; b=fh4rUfafImv5E3+dzUBzSyAH0UxJ7P3v0guFOghHpGgKw9htNv3wRwNlk/xbUDMChq XbxoHEcBCmp8UmE4t7gLmHvDqJmvbWqC/9wCL69AahAD+gc74yvGXWzpjpq544e/27Fh StqpVQxAKaCEi7Wx+1cMuElM2vhax1Lv8tLM0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:cc:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=UpPxx1YinzHdNXIYEbb5PLk/P6GCs/fKCbfPRhoFywr/WmZL1Otu3YB+/UADOQW65c 6ME/wGg0rPNiMMTyJdUMhmi7gdbJKhRODI6nUSLZjaLzUs6xCEGUqej/6+0onQG/o3AZ WLTvXvvvbtR4CAYJHK2Q6OQv6Dt1qpmjYEbY4= Received: by 10.140.251.5 with SMTP id y5mr364632rvh.17.1276190147090; Thu, 10 Jun 2010 10:15:47 -0700 (PDT) Received: from localhost (c-76-98-96-154.hsd1.nj.comcast.net [76.98.96.154]) by mx.google.com with ESMTPS id i19sm205462rvn.23.2010.06.10.10.15.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Jun 2010 10:15:43 -0700 (PDT) From: Eric Sherman To: Daniel Goldin In-reply-to: References: Date: Thu, 10 Jun 2010 13:15:40 -0400 Message-Id: <1276189944-sup-3195@changeling.local> User-Agent: Sup/git Cc: sup-talk Subject: Re: [sup-talk] error message running sup 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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