jsc@cs.utexas.edu (12/20/89)
I've just brought up a network of 6 Sun 3/80's running SunOS 4.03 and a resume tracking system called RESUMIX. One station acts as a file server, the other five are diskless. When a user logs into a client, and uses yppasswd to change their password, the password gets changed in the YP database, but the client is not updated until the next time root pushes the passwd file with yppush. The support folks tell me this is the functionality of 4.03. Is that true? Is so, how do some of the rest of you work with this? Do you put yppush in crontab? I'm new as a Sun administrator, and your help would be appreciated. TIA, Scott Carr Sequent Computer Systems (503) 526-5940
jms@tardis.tymnet.com (Joe Smith) (01/04/90)
In article <4002@brazos.Rice.edu> sequent!jsc@cs.utexas.edu writes:
:X-Sun-Spots-Digest: Volume 8, Issue 228, message 14 of 18
:yppasswd to change their password, the password gets changed in the YP
:database, but the client is not updated until the next time root pushes
:the passwd file with yppush. The support folks tell me this is the
:functionality of 4.03. Is that true? Is so, how do some of the rest of
:you work with this? Do you put yppush in crontab?
To do an automatic yppush whenever anyone runs yppasswd, simply add "-m"
to the line in /etc/rc, as in:
if [ -f /usr/etc/rpc.yppasswdd ]; then
rpc.yppasswdd /etc/passwd -m; (echo -n ' yppasswdd') >/dev/console
fi
The -m tells yppasswdd to do the equivalent of "(cd /var/yp; make passwd)"
whenever yppasswd is invoked from any client.
Joe Smith (408)922-6220 | SMTP: JMS@F74.TYMNET.COM or jms@gemini.tymnet.com
BT Tymnet Tech Services | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms
PO Box 49019, MS-D21 | PDP-10 support: My car's license plate is "POPJ P,"
San Jose, CA 95161-9019 | humorous dislaimer: "My Amiga speaks for me."