[1551] in Kerberos_V5_Development
Re: kdc.conf [realms] section
daemon@ATHENA.MIT.EDU (Sam Hartman)
Tue Aug 13 12:51:40 1996
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: raeburn@cygnus.com, krbdev@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 13 Aug 1996 12:51:36 -0400
In-Reply-To: "Barry Jaspan"'s message of Tue, 13 Aug 1996 12:03:06 -0400
>>>>> "Barry" == "Barry Jaspan" <bjaspan@MIT.EDU> writes:
Barry> One occurs to me right away -- one server acting as
Barry> slave for one realm and master KDC/admin server for
Barry> another.
Barry> Hmmm. When would this arrangement actually be used?
Barry> * take kadmind offline for each kprop run; dump the
Barry> database, merge, reload
Barry> Perhaps I'm missing something obvious, but I don't see why
Barry> you would have to take kadmind offline for this operation.
Barry> "dump, merge, reload" is in fact the solution I would
Barry> recommend for this arrangement.
If I modify the data with kadmin between the dump and the
reload step, I lose the changes.
Barry> We would have to make sure that kadmind would not get
Barry> confused when another realm's data appeared in its
Barry> database, of course. But we did actually have multiple
Barry> realms in our OV KDC (granted we didn't use any but one of
Barry> them very often) and didn't notice any problems.
Barry> Barry
