Morning:
Thanks for Ann Majeske, Pat O'Brien, and John Venier.
The problem over here is that our NIS does not configure right. On all
three slave nodes, they run (cron job) ypxfr passwd.bynamd/byuid once an
hour, this explains why the password change would take time to become
effect. On the server node, there is no slave server has ever been defined.
I add 3 slave servers to the domain and propagate the newly create
ypservers to the slave servers. After that, password changes (by yppasswd
and dxaccounts) take effect immediately.
The procedure I took is:
# cd /var/yp
# /var/yp/makedbm -u gemc/ypservers > newmap (where gemc is our domain id)
Edit the newmap and add host names of 3 slave servers.
# /var/yp/makedbm newmap ypservers
# mv newmap.dir gemc/ypservers.dir
# mv newmap.pag gemv/ypservers.pag
# /var/yp/yppush ypservers
Thanks.
Original question:
We have installed NIS on four of our Tru64 (V4.0D) Alphas. Yesterday
afternoon, I used dxaccounts to modify a user account password, the
modification took effect on all 4 systems rightaway. However, if I use
yppasswd, the change won't take effect until later. This morning, I ran
dxaccounts again to modify a password, 10 minutes later, the new password
is still not working...
What is the proper method to change password and let it takes effect
immediately in a NIS environment? Should I use yppush after yppasswd?
Warren Liang
SMS/Marconi
(714) 986-8342
Warren.Liang_at_Marconi.com
Received on Wed Mar 14 2001 - 15:50:48 NZDT