Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've had a user that couldn't login and thought the account was locked. From what I can tell, the account was not locked and had not expired yet it behaved as though it was expired and needed to be reset. Resetting the password with passwd resolved the issue. Maybe someone can point me to something I'm missing.
Here are the details:
This is an application account used on 4 systems and the passwords are manually set to match.
cat /etc/passwd shows as expected: accountname:x:4101:2100:accountdescription:/sbin/nologin
cat /etc/shadow also shows as expected: accountname:passwordhash:14122:0::14:::
faillog only showed a latest value for 1 system. All of them showed 0 failures and 0 maximum.
sudo faillog -u accountname
Username Failures Maximum Latest accountname 0 0 Mon Dec 29 14:30:03 -0500 2008 on IPaddress
chage showed Aug 31 on 2 systems and May 8 on the other 2:
sudo chage -l accountname
Last Change: Aug 31, 2008
Password Expires: Never
Password Inactive: Never
Account Expires: Never
So from everything I can see here, we have policies in login.defs that were likely applied after the accounts were created or the accounts were changed with chage to override those settings. Everything here seems to indicate that the passwords should never expire or become inactive (Maximum -1, Inactive -1).
Am I reading something wrong or missing some other commands that would help me?
By the sounds of it, the accounts hit the 90 definition rule and that took precedence over everything else. If the accounts were created before the rules were put in place that could confuse the system, but if not then I'm at a loss of to why that should have happened.