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
> a...@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
[email protected]
http://rubyforge.org/mailman/listinfo/sup-talk
