cks@hawkwind.utcs.toronto.edu (Chris Siebenmann) (08/30/90)
I'm trying to set up a (slave) authentificated nameserver on a
diskless client here as a prelude to going to UPGRADED security, as
the documentation says you have to. However, I can't get a
kerberos-authentificated nameserver started on the client; it dies
immediately on startup, leaving the cryptic message:
Aug 29 21:36:04 localhost: 322 named: restarted
Aug 29 21:36:06 localhost: 322 named: bad krb_svc_int call 70
in /usr/spool/mqueue/syslog. The kerberos-authentificated named starts
fine on the server (which is also the kerberos and named master). The
client has a /etc/srvtab, an /etc/krb.conf, etc, all seeming to point
(correctly) at the master and with the right realm name. The master is
a DECStation 5000, the diskless client a DECStation 2100; both are
running Ultrix 4.0+mandatory upgrade tape. I've entered and re-entered
the client's named/<name> and hesiod/<name> entries in the Kerberos
database several times, with no apparent changes. Both the server and
the client have been rebooted several times.
Does anyone know what this error message means, or have any idea? Has
anyone actually done this? Is Kerberos and the enhanced security worth
this much effort? Does the Ultrix 4.0 NFS use Kerberos
authentification?
--
"You don't *run* programs on Ultrix." - Mark Moraes
"Right, you chase them." - Rayan Zachariassen
cks@hawkwind.utcs.toronto.edu ...!{utgpu,utzoo,watmath}!utgpu!cks