From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] sup ignoring SIGTERM?
Date: Fri, 07 Aug 2009 12:40:18 -0400 [thread overview]
Message-ID: <1249662782-sup-638@pion.club.cc.cmu.edu> (raw)
In-Reply-To: <20090807103151.GA20799@chistera.yi.org>
Excerpts from Adeodato Sim?'s message of Fri Aug 07 06:31:51 -0400 2009:
> 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'
> from .../bin/sup:132
I've just posted a patch that should fix this.
next prev parent reply other threads:[~2009-08-07 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 14:09 Adeodato Simó
2009-08-05 20:03 ` William Morgan
2009-08-05 20:25 ` Nicolas Pouillard
2009-08-05 21:24 ` William Morgan
2009-08-06 17:53 ` William Morgan
2009-08-06 18:09 ` Nicolas Pouillard
2009-08-06 23:56 ` Ben Walton
2009-08-05 20:35 ` Ben Walton
2009-08-05 21:28 ` Edward Z. Yang
2009-08-06 18:37 ` Adeodato Simó
2009-08-07 1:38 ` William Morgan
2009-08-07 10:31 ` Adeodato Simó
2009-08-07 16:40 ` Rich Lane [this message]
2009-08-08 9:23 ` Adeodato Simó
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=1249662782-sup-638@pion.club.cc.cmu.edu \
--to=rlane@club.cc.cmu.edu \
/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