I'm administering a Tru64 v5.0A, patch level 2 system. The system is
running with enhanced security. One of my users is having problems logging
onto the system. In particular after he enters his password he is told
that his account is disabled. This is not too unusual on this sytem
(people forget passwords and keep guessing until the "maximum attempts"
limit is reached, etc).
After I execute the command
# usermod -x administrative_lock_applied=0 <username>
His account is still disabled. This is odd. Normally the command above
unlocks user accounts just fine.
When I go into dxaccounts and look at the status of his account, the "Lock
Account" checkbox is checked. If I uncheck it and then apply the
modification, there is no error. I get "User <username> modified
successfully". However if I then immediately open the status of his
account again I see that the "Lock Account" checkbox is still checked.
I notice that the "Unlock Interval" parameter (as displayed in dxaccounts)
is set to 1 hour. I understand that to mean that his account can't be
unlocked until an hour or more has passed since it got locked. However, I
am confident that I tried the usermod command above long after an hour
after his account might possibily have been locked. However, I do admit
that I don't totally understand how enhanced security works and that
perhaps I am doing something wrong without realizing it.
So far, no other users are having this problem. What should I be looking
at to resolve this?
Thanks.
Peter
Received on Tue Jan 16 2001 - 14:01:28 NZDT