[16568] in Athena Bugs
Re: [Greg Rutledge : netscape]
daemon@ATHENA.MIT.EDU (t. belton)
Fri Dec 18 10:39:22 1998
Date: Fri, 18 Dec 1998 10:39:20 -0500 (EST)
From: "t. belton" <tbelton@MIT.EDU>
To: Abby Fox <ajfox@MIT.EDU>
Cc: bugs@MIT.EDU
In-Reply-To: <199812181519.KAA18799@whirlwind.mit.edu>
On Fri, 18 Dec 1998, Abby Fox wrote:
> 1. Is this actually a behavior change?
>
> 2. What's the right thing to tell a private ws owner about such
> things? (In particular, I believe he's using an SGI: should we
> discourage leaving Netscape running given things like the AFS-hosage
> mystery, tell him how to get longer tickets, something else?)
I'm none too clear on what happens when your tickets expire, but isn't
your kerberos identity involved in figuring out which afs lockers you can
attach? Or - flip that around - do attached afs lockers suddenly become
unavailable when your tickets expire?
At any rate ... Netscape could care less about your kerberos ID, but if
you pull infoagents out from under it while it's running, it gets very
unhappy.
I don't know about this afs mystery you mention, but I'm willing to bet
that the problem is afs visibility, not kerberos per se. There are certain
files in infoagents that Netscape needs to be able to read at all times
while it's running.
Longer tickets should solve the problem, but why would you need to keep
Netscape running overnight? There's no all-night computation job where
it's required. The real solution is to not leave Netscape running. (How
"annoying" can it possibly be to launch Netscape every morning?)
The even realer solution is to *log off the freakin' machine,* private or
no, and not have the tickets expire in the first place ... but I recognize
I'm a lone zealot ... half of I/S stays logged in on their private ws's
24/7.
-Todd
