[941] in SIPB bug reports
GRIPE about XRN 6.7 (for X11R4)
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Sun Mar 11 20:30:15 1990
Date: Sun, 11 Mar 90 20:29:44 -0500
From: Jonathan I. Kamens <jik@pit-manager.MIT.EDU>
To: grogo@ATHENA.MIT.EDU
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: grogo@ATHENA.MIT.EDU's message of Thu, 1 Mar 90 15:00:58 -0500 <9003012000.AA15517@WILLIAM-GIBSON.MIT.EDU>
From: grogo@ATHENA.MIT.EDU
Date: Thu, 1 Mar 90 15:00:58 -0500
If I log out without explicitly quitting XRN, it will give me a
message such as " an XRN process of yours is running on machine
such-and-such. If you're not using it, remove .xrnlock" or
something like that. It's a pain because I ahve to rm .xrnlock
every time explicitly before I can invoke xrn again.
It is generally a bad idea to log out without exiting from xrn
explicitly, so you should exit before logging out.
However, I have fixed up the xrn source code a little bit so that it
*should* delete your .xrnlock and update your .newsrc if you log out
without quitting explicitly. The changes I have made should take
effect in the sipb locker early tomorrow (Monday 3/12) morning.
Thank you for reporting the problem.
--> Jonathan Kamens
Student Information Processing Board (SIPB) member
Project Athena Watchmaker and User Consultant
jik@Athena.MIT.EDU
