Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!mit-eddie!snorkelwacker!apple!agate!shelby!MIT.EDU!jon
From: jon@MIT.EDU (Jon A. Rochlis)
Newsgroups: comp.protocols.kerberos
Subject: Re: kadmind run out of rc.local and kprop/kpropd comments
Message-ID: <9009131359.AA08848@delwin.MIT.EDU>
Date: 13 Sep 90 13:59:28 GMT
References: <9009130750.AA02318@ack.Stanford.EDU>
Sender: daemon@shelby.Stanford.EDU
Organization: The Internet
Lines: 12

I don't know why kadmind is losing from rc.local, but a word of
caution.  We have never automatically restarted the write paths to the
database after a crash for database consistency reasons.  Before
starting kadmind we always check to be sure last write to the dbm
database happened well before the crash.  If not, we usually dump the
database, look at the ascii dump (comparing it to last night's slave
dump), and reload, just for paranoia's sake.

We could automate the process, I suppose, but our master hardly ever
goes down (124 days up as of today), so it hasn't seem worthwhile.

		-- Jon