[1946] in Kerberos_V5_Development
Re: Configuration directories
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Tue Nov 12 16:57:46 1996
Date: Tue, 12 Nov 1996 16:56:14 -0500
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Sam Hartman <hartmans@MIT.EDU>
Cc: Greg Hudson <ghudson@MIT.EDU>, source-developers@MIT.EDU, krbdev@MIT.EDU
In-Reply-To: Sam Hartman's message of 11 Nov 1996 13:20:13 -0500,
<tsl7mns8peq.fsf@tertius.mit.edu>
From: Sam Hartman <hartmans@MIT.EDU>
Date: 11 Nov 1996 13:20:13 -0500
>>>>> "Greg" == Greg Hudson <ghudson@MIT.EDU> writes:
Greg> 4. Look for configuration files in /etc and in
Greg> @sysconfdir@; if both are present, merge them together with
Greg> the file in /etc taking precedence. This is what Kerberos 5
Greg> release 1.0 will do.
I told you this is the case, but after glancing at the code,
I'm no longer sure. It may only read the file in @sysconfdir@ if the
file in /etc is present. I'll open a doc bug once I figure out what
is happening. (I realize this is somewhat of a tangent.)
This is what will eventually happen (with the precedence order probably
being ~/.krb5rc:/etc:@sysconfdir@).
The other problem with (2) always use @sysconfdir@, is that if you have
multiple programs compiled with different @sysconfdir@'s, the result can
be highly confusing. An example of this was that with the original
krb.conf --- some programs looked for this file in /etc/krb.conf.
Others looked in /etc/athena/krb.conf, and still others looked in
/usr/local/etc/krb.conf or /usr/cygnus/etc/krb.conf. The result was a
complete and total mess.
This is why for krb5, I very much discourage the use of @sysconfdir@,
and hope that everyone will just always install krb5.conf in
/etc/krb5.conf. Being able to have user-specific overrides in ~/.krb5rc
solves a different problem, but that's why eventually I'll try to handle
the merge case.
- Ted
