Problem with locked accounts on 5.0a - bug?

From: Ken Kleiner <ken_at_cs.uml.edu>
Date: Fri, 05 May 2000 12:54:57 -0400

Hello...

  I have Tru64 5.0a running with NIS and enhanced security.

  When I use : useradd -x distributed=1 administrative_lock_applied=0
new_user_name, the
/var/yp/src/prpasswd file DOES NOT get the u_lock_at_ entry put into it for
that user. If I try using 'usermod' to set it after the account is created,
it also does not work.

  This is also true when using 'dxaccounts'.

  However, when I use 'edauth user_name' and manually enter 'u_lock_at_' in
that user's database entry, the account is properly unlocked and I can log
in from a nis client.

  Is this a bug or am I missing something very simple?

  Thanks in advance...will summarize.

-Ken Kleiner
System Manager
Computer Science Dept
Umass Lowell
ken_at_cs.uml.edu
Received on Fri May 05 2000 - 16:52:21 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:40 NZDT