[26737] in Athena Bugs
Re: linux 9.4.22: pine
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Feb 7 11:31:55 2006
From: Greg Hudson <ghudson@mit.edu>
To: Jonathan D Reed <jdreed@mit.edu>
In-Reply-To: <200602071541.k17FfMXR003601@infinite-loop.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Tue, 07 Feb 2006 11:31:07 -0500
Message-Id: <1139329867.8791.282.camel@egyptian-gods.mit.edu>
Mime-Version: 1.0
X-Spam-Score: 1.217
X-Spam-Level: * (1.217)
X-Spam-Flag: NO
Cc: astronut@mit.edu, bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
On Tue, 2006-02-07 at 10:41 -0500, Jonathan D Reed wrote:
> Writing a simple signal handler in perl indicates
> that the SIGHUP is in fact sent upon disconnection, however
> pine never handles it.
I did a little testing, and I'm not sure this is true. I sshed into a
machine as myself, ran pine, started composing a message, attached to
the pine process as root from a separate session, and then terminated
the initial ssh connection. The SIGHUP handler appeared to run.
I suggest an alternate theory: pine can't write the file because sshd or
login.krb5 has destroyed the user's tokens. Ideally, we would locally
hack Pine to save the file into /var/tmp when this happens, but I'm not
sure whether we'll allocate the resources to do that.
