From mboxrd@z Thu Jan  1 00:00:00 1970
From: rlane@club.cc.cmu.edu (Rich Lane)
Date: Fri, 07 Aug 2009 12:40:18 -0400
Subject: [sup-talk] sup ignoring SIGTERM?
In-Reply-To: <20090807103151.GA20799@chistera.yi.org>
References: <1249481294-sup-9967@chistera.yi.org>
	<1249502171-sup-8079@masanjin.net>
	<20090806183725.GA8363@chistera.yi.org>
	<1249609105-sup-5858@masanjin.net>
	<20090807103151.GA20799@chistera.yi.org>
Message-ID: <1249662782-sup-638@pion.club.cc.cmu.edu>

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.