[234] in Info-AFS_Redistribution
Re: Ticket lifetime
daemon@ATHENA.MIT.EDU (Tony_Mauro@transarc.com)
Mon Jul 22 10:34:56 1991
Date: Mon, 22 Jul 1991 09:30:37 -0400 (EDT)
From: Tony_Mauro@transarc.com
To: Info-AFS@transarc.com
The AFS 3.1 Release Notes also discuss this issue on pages 6 and 7.
In fact, you need to change the maximum lifetime of only *one* of
"afs" and "krbtgt.etc", since AFS login sets ticket lifetime to the
smallest of three lifetimes: these two, and the one in the issuer's
AuthDB entry. Klog considers these three plus the lifetime requested
with the -lifetime switch (if it is used).
Tony Mauro
Transarc
---------- Forwarded message begins here ----------
Date: Sat, 20 Jul 1991 19:19:28 -0400 (EDT)
From: John Gardiner Myers <jm36+@andrew.cmu.edu>
To: Info-AFS@transarc.com
Subject: Ticket lifetimes
CC: umich-systems@itd.umich.edu, Info-AFS@transarc.com
Sites that have upgraded from an older version of AFS to AFS 3.1
should check their ticket lifetimes. The AFS clients have changed
from asking for a ticket with a 25-hour lifetime to asking for a
ticket with the longest possible lifetime. When we first started
using the new clients, we had tickets with 100-hour lifetimes.
If necessary, administrators might want to use kas to modify the
maximum lifetimes of the "krbtgt.CELL.NAME.IN.UPPER.CASE" and "afs" to
"25:00".
--
_.John G. Myers Internet: John.G.Myers@andrew.cmu.edu
(412) 268-2314 LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up
