LogoIts possible that sometime in your short, meaningless life, you may need to create an account that has a password that is set to never expire. This is somethimes the case with headless accounts and specialty accounts such as the type you might have to setup for monitoring or security scanning. You might also find yourself setting up shared headless accounts that have locked passwords in order to block direct logins. This second scenario can be especially troublesome when this is some sort of application or database user with cron jobs, as even an account without a password and expire and lock. If this occurs all of a users cron jobs will fail. All because the account expired.
expire
You are not allowed to access to (crontab) because of pam configuration.
PD Donut Guy with ShadowHey look a real live Linux post. Sure enough and right as rain I am back with something that is not about networking (yea!) and not about Solaris (yuck). In this case we had a user who is in our database team who was attempting to make modifications to the oracle user's crontab. However they kept running into the error below
RHEL – Managing Passwords with Chage
To understand the chage command if might be best to make sure that you understand the /etc/shadow file, so lets look at a line from mine. Note that ":" is the field separator.