When an attempt is made to yppasswd a user that has the crypt string
in the passwd source file, and no entry in the passwd.adjunct file,
yppasswdd reports that there's no password for the user:
dylan$ yppasswd mvpel
Enter existing login password:
New Password:
Re-enter new Password:
passwd: System error: no nis password for mvpel.
Permission denied
dylan$
When rpc.yppasswdd restarted without reference to the adjunct file,
the change works fine:
dylan$ yppasswd mvpel
Enter existing login password:
New Password:
Re-enter new Password:
passwd: password successfully changed for mvpel
dylan$
This behavior makes it very difficult to do a phase-in of
passwd.adjunct, since it would appear that any user not configured
with it wouldn't be able to change their password via the yppasswdd.
As I see it, it should only attempt passwd.adjunct updates for
accounts which have the ##user flag, and behave exactly as it would
without passwd.adjunct for accounts which don't.
Is this a bug, or am I missing a step somewhere?
-Michael Pelletier.
--
Message posted using http://www.talkaboutcomputing.com/group/comp.sys.sun.admin/
More information at http://www.talkaboutcomputing.com/faq.html