[2109] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: Krb5-1.0 and t_kdb - It works on HP

daemon@ATHENA.MIT.EDU (Ezra Peisach)
Tue Dec 10 07:23:56 1996

To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
Cc: Ken Hornstein <kenh@cmf.nrl.navy.mil>, deengert@anl.gov, krbdev@MIT.EDU,
        Paul A Vixie <paul@vix.com>, Andrew Hobson <ahobson@mindspring.com>,
        Dave McGuire <mcguire@neurotica.com>, Joe Gross <jgross@uiuc.edu>
In-Reply-To: Your message of "Tue, 10 Dec 1996 02:26:03 EST."
             <9612100726.AA12861@dcl.MIT.EDU> 
Date: Tue, 10 Dec 1996 07:23:41 EST
From: Ezra Peisach <epeisach@MIT.EDU>


We are already using configure to determine the location of the replay cache.
We check for the existance of /usr/tmp, /var/usr/tmp, /var/tmp and /tmp
in that order. Whoever exists first wins.

The real problem is that for database locking - you need a filesystem with
more specific characteristics - which may be more difficult to determine.

	Ezra

home help back first fref pref prev next nref lref last post