bill@pslu1.psl.wisc.edu (Bill Roth) (11/14/90)
Hello. Has anyone had any trouble setting up Hesiod to distribute the passwd file? We've just set it up here, and we keep getting the message Kerberos Init- ialization error, though we set it up initially to run without kerberos? Has anyone has similar experiences? -- ------------------------------------------------------------------------ Bill Roth, University of Wisconsin Physical Sciences Laboratory email: bill@pslu1.psl.wisc.edu bill@wiscpsl.bitnet / (608)-873-6651
schemers@vela.acs.oakland.edu (Roland Schemers III) (11/22/90)
Hello! I am setting up hesiod to distribute the passwd file and have gotten it to work. My main question is what is the correct way to maintain the passwd file under the following conditions: o The primary server is the host where the 'real' /etc/passwd file lives. o We are also using mkpasswd on the primary server. I know I can link the /var/dss/namedb/src/passwd file to /etc/passwd, but which way should it go? It seems like it would be: ln -s /etc/passwd /var/dss/namedb/src/passwd So what happens to /etc/passwd.{pag,dir} when someone changes their password remotely, and the hesupd updates /var/dss/namedb/src/passwd? It seems like it would get out of sync unless the hesupd knows about the hashed passwd file. Also what about the opposite when someone on the primary server changes their password? Does this change not get propagated until the hesiod passwd.db is re-made? After all is said and done, what has to be done to keep all these files in sync? It almost seems like a cron job is needed to run mkpasswd and/or /var/dss/namedb/make passwd periodically. Thanx for any help. Roland -- Roland J. Schemers III Systems Programmer schemers@vela.acs.oakland.edu (Ultrix) Oakland University schemers@argo.acs.oakland.edu (VMS) Rochester, MI 48309-4401 ~Disclaimer::Disclaimer() { reboot(RB_HALT); } (313)-370-4323