>Have I missed something?
Nope. I see the same thing. We run NIS+ and when I recently cleared
a passwd with admintool, on the next login /usr/bin/passwd was run
for that user and it could not find the id (since it was in NIS+ and
not in /etc/passwd).
>When a person's password is expired, the login program is calling
>/usr/bin/passwd. Arrgh. It's running NIS+, of course, so this does NO GOOD.
Way back in the cluttered recesses of my mind, I remember reading some
doc on an early version of Solaris 2.X (X=0or1) which said that
/usr/bin/passwd would look for the id in NIS+ (and/or NIS) if it did
not exist in /etc/passwd. I don't remember testing it though.
Anybody know if this was ever the case (at least in the doc)?
Is there a compelling reason not to do it this way?
>So, apart from going to all hundred or so of my machines and making a link of
>/usr/bin/passwd to nispasswd, could I somehow coerce login to call nispasswd?
Maybe if you have a dir like /usr/local/bin in your PATH before
/usr/bin (for all users) then just put a passwd script in there that
does what you want. We do something similiar to that (we have users
from 2 NIS+ domains using our systems so we put the "-D domain" option on
nispasswd for them).
>Systems Administrator (214) 578-6189
>Inet, Inc. You can have your cake and eat it, too.
Glenn T Barry
Voice: (404)727-5637 Fax: (404)727-5611
Emory University, Dept of Math and CS, Atlanta,GA 30322-2390