Subject: kdc rc.d startup [was: rc.d: time synchronization issues ...]
To: None <tech-userlevel@NetBSD.org>
From: Luke Mewburn <lukem@NetBSD.org>
List: tech-userlevel
Date: 03/16/2005 21:45:56
--buDNgeHiu+HCsDEc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Mar 16, 2005 at 10:24:20AM +0000, Alistair Crooks wrote:
  | 3. forget about problems with time in kdc or named. (I'm not really
  | serious here)

A question for the kerberos gurus ...

Does "kdc" need to start so early in the boot process?

What other services start at boot that might depend upon kdc ?
nfsd ? sshd ? racoon ?
Various other login servers (started after LOGIN) ?

Is there any reason that we can't move kdc a bit later,
to sometime between "SERVERS" and "DAEMON", and explicitly
depending upon ntpdate?



Thanks,
Luke.

--buDNgeHiu+HCsDEc
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iD8DBQFCOA5kpBhtmn8zJHIRAl3LAKDUCDQbMOrOa9wQm+UsC7oAoDiNuQCdHC0b
TQZhzH2PMCjiSQsOKuj2a6Q=
=HH/8
-----END PGP SIGNATURE-----

--buDNgeHiu+HCsDEc--