From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] trying sup again, couple of crashes, etc
Date: Fri, 15 Jan 2010 02:03:01 +0200 [thread overview]
Message-ID: <1263511303-sup-1489@tilus.net> (raw)
In-Reply-To: <4B4EB5A9.8050001@exys.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
next prev parent reply other threads:[~2010-01-15 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 6:11 Arvid Picciani
2010-01-15 0:03 ` Tero Tilus [this message]
2010-01-17 16:06 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1263511303-sup-1489@tilus.net \
--to=tero@tilus.net \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox