Problem
Some or all of my users, possibly including root, are unable to use passwd(ADM) to change their password. If root is affected, then root is unable to change other users' passwords as well. The user is prompted for the old and new password, but after entering the password the second time, they get the message:
Password cannot be changed; see Account Administrator.
In some cases, only root is affected; in others, all or some
users are affected. You may find you can change passwords in
Maintenance mode, but not as root in multiuser mode. Cause
There can be many causes of this error message related to problems with the security subsystem, but one simple cause is an incorrect ulimit(C) setting.
ULIMIT is used to limit the size of a file that can be created
on a system. It can be set several ways.(1) There is a kernel tunable variable ULIMIT.
(2) The variable ULIMIT can be set in /etc/default/login.
(3) It can be set by the command ulimit(ADM) in the bourne or
korn shells. This command can also be run in root's .profile.(4) It can be set programatically, using the ulimit(S) system call.
Note that only root can set the ulimit higher than what is set by the kernel tunable or /etc/default/login.
The unit for ULIMIT is disk blocks, 512 bytes each. Since the
maximum file size is 2GB or 2147483648, the maximum value of
ULIMIT is 4194303. If ULIMIT is set higher than this, by any
of the above methods, it causes the passwd(ADM) command to fail.If ULIMIT is set to a bad value in /etc/default/login, but if a user's .profile sets it to a lower value, then you will see the behavior where some users can change their passwords, while others can't.
Since the /etc/default/login isn't parsed in Maintenance mode, this explains the behavior where root can change passwords in Maintenance mode, but not multiuser mode.
Solution
The solution is to determine where the bad ULIMIT value is set, then fix it. The most likely culprit is /etc/default/login. It is possible, but unlikely, that the kernel tunable was changed.
If this symptom is not caused by a bad ULIMIT value, then the
security subsystem is likely corrupted. Try running the repair
utilities in the articles referenced below.This will be addressed in a future release of SCO OpenServer 5.
See also
ta104582, "Non-root users are unable to write to a file > 1073741312 (1GB)."
ta105410, "Filesystem Repair Utilities for SCO Unix Release 3.2 Version 4.2."
ta105411, "Filesystem Repair Utilities for SCO OpenServer 5.0.0 and 5.0.2."