Sorry about this -- answering my own question.
The problem was passwd.lock. Deleted and it works fine. However, in general it is better to:
rm *- (passwd-, shadow-, etc)
rm *.lock (passwd.lock, etc)
Make sure before you do that you are only getting passwd, shadow, and group.
*********** REPLY SEPARATOR ***********
On 8/28/01 at 5:01 PM Gregory Wood wrote:
There is probably an easy answer for this -- but I don't know it.
I was operating remotely, changing a password for a user and got the message: segmentation fault. I went to the server and looked over the files and the processes and found nothing. So, I ran the passwd program again and this time I got: passwd is locked. Try again later.
So what's the deal?
Thanks in advance.