From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.7.146 with SMTP id d18cs196300ebd; Thu, 14 Jan 2010 16:03:12 -0800 (PST) Received: by 10.224.59.203 with SMTP id m11mr1663402qah.238.1263513791513; Thu, 14 Jan 2010 16:03:11 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 6si3213082qwd.46.2010.01.14.16.03.11; Thu, 14 Jan 2010 16:03:11 -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 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id ED14515B802E; Thu, 14 Jan 2010 19:03:10 -0500 (EST) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id A4405185830C for ; Thu, 14 Jan 2010 19:03:02 -0500 (EST) Received: by kuovi.tilus.net (Postfix, from userid 1000) id 6ABEB6011; Fri, 15 Jan 2010 02:03:01 +0200 (EET) From: Tero Tilus To: sup-talk In-reply-to: <4B4EB5A9.8050001@exys.org> References: <4B4EB5A9.8050001@exys.org> Date: Fri, 15 Jan 2010 02:03:01 +0200 Message-Id: <1263511303-sup-1489@tilus.net> User-Agent: Sup/git Subject: Re: [sup-talk] trying sup again, couple of crashes, etc 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 Arvid Picciani, 2010-01-14 08:11: > So heres is how my sup experience has been so far: awesome idea, but > unusable. I see sup's offered you a rough ride... :( Is this with ruby 1.9? If so, have you tried with 1.8.x? > sup-add nukes itself: > > Error: the index is locked by another process! User '' on > host '' is running with pid . > The process was alive as of at least 14 seconds ago. > > Should I ask that process to kill itself (y/n)? y > Ok, trying to kill process... > Terminated > aep@barf: ~/kram/mainline Looks like it somehow failed to write or read the contents of lockfile. When pid is nil, lock resolver ends up calling Process.kill('TERM', 0) killing the process itself. Can you reproduce? > sup then takes around 20 seconds per message (100% cpu usage) Thats insane. Could you try that again with ruby-prof and post the profile so we can figure out what gives? $ sudo gem install ruby-prof $ ruby-prof -p graph_html -f sup-profile.html sup -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk