[sup-talk] sup ignoring SIGTERM?
dato at net.com.org.es
Fri Aug 7 06:31:51 EDT 2009
+ William Morgan (Thu, 06 Aug 2009 18:38:53 -0700):
> Reformatted excerpts from Adeodato Simó's message of 2009-08-06:
> > Everything seems to work fine as of 3478e40, including sup terminating
> > upon SIGTERM. If I may, I'd suggest normal termination instead of
> > raising an exception. IMHO, it is expected that programs that capture
> > SIGTERM, will do cleanup and exit normally, rather than behave as if
> > an error had happened.
> Good idea. Try it now.
Ah, excellent: works as suggested now.
Regarding 57dea7a (refactor index locking interaction and replace
suicidemanager), I'll note that at least on my system, and after having
moved to Xapian, those codepaths no longer execute. That is, if a sup is
running and a second one is started, it never gets to ask whether to
suggest dieing to the first one, because this second one dies with:
[Fri Aug 07 12:31:05 +0200 2009] using character set encoding "UTF-8"
[Fri Aug 07 12:31:05 +0200 2009] using index Redwood::XapianIndex
[Fri Aug 07 12:31:05 +0200 2009] dynamically loading setlocale() from libc.so.6
[Fri Aug 07 12:31:05 +0200 2009] setting locale...
.../lib/sup/xapian_index.rb:24:in `initialize': Resource temporarily unavailable - /home/adeodato/.sup/entries.db (Errno::EAGAIN)
from .../lib/sup/xapian_index.rb:24:in `new'
from .../lib/sup/xapian_index.rb:24:in `initialize'
from .../bin/sup:132:in `new'
- Are you sure we're good?
-- Rory and Lorelai
More information about the sup-talk