[9976] in SIPB bug reports
Re: pine-sipb wrapper
daemon@ATHENA.MIT.EDU (Jacob Morzinski)
Tue Jan 20 15:53:37 2004
From jmorzins@MIT.EDU Tue Jan 20 20:53:37 2004
Return-Path: <jmorzins@MIT.EDU>
Delivered-To: bug-sipb-mtg@CHARON.mit.edu
Received: (qmail 26974 invoked from network); 20 Jan 2004 20:53:37 -0000
Received: from pacific-carrier-annex.mit.edu (18.7.21.83)
by charon.mit.edu with SMTP; 20 Jan 2004 20:53:37 -0000
Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])
by pacific-carrier-annex.mit.edu (8.12.4/8.9.2) with ESMTP id i0KKraRB021000;
Tue, 20 Jan 2004 15:53:36 -0500 (EST)
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
by central-city-carrier-station.mit.edu (8.12.4/8.9.2) with ESMTP id i0KKrZIg029773
for <bug-sipb@mit.edu>; Tue, 20 Jan 2004 15:53:35 -0500 (EST)
Received: from mit.edu (QUICHE-LORRAINE.MIT.EDU [18.187.1.71])
)
by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id i0KKrYRj014514
for <bug-sipb@mit.edu>; Tue, 20 Jan 2004 15:53:34 -0500 (EST)
Message-ID: <400D954E.1070302@mit.edu>
Date: Tue, 20 Jan 2004 15:53:34 -0500
From: Jacob Morzinski <jmorzins@MIT.EDU>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20040102
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bug-sipb@MIT.EDU
Subject: Re: pine-sipb wrapper
References: <400C72A0.7090105@mit.edu> <1074603363.16682.75.camel@error-messages.mit.edu> <400D38A1.10605@mit.edu> <1074608738.467.2.camel@equal-rites.mit.edu>
In-Reply-To: <1074608738.467.2.camel@equal-rites.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I've modified the wrapper script to use the same *-noask files as the
athena wrapper script uses. The sipb wrapper checks the date of
.athena-sipb-pine-noask and asks the user to re-answer the question if
it's been a year since they last answered. (It leaves the user alone if
they picked .athena-pine-noask.)
/afs/.sipb/project/sipb/src/pine/share/pine-sipb
It would be nice to have a lockfile mechanism that tries to prevent
running multiple pine instances, but writing a scheme that protects
ordinary users from stale lockfiles is more effort than I have time for
right now. ("It says it won't start because I shouldn't run more than
one pine at once, but I'm not running any other pines right now.")
Apparently there are a fair number of people who have been habitually
answering "2" to the athena-wrapper question (let me use sipb pine for
now, ask me again later) -- I've seen two people like this in the sipb
office in the past three days. Maybe the jar to their habits will
encourage them to pick one.
-Jacob
