cronjab

later I found out.

if account is locked then jobs which are scheduled in crontab of that particular user will be executed without any problem.

where as

if his account is expired then jobs of his crontab will never be executed and throws error with bad user in /var/cron/log file.

anesh at 2007-7-5 17:05:58 >

I am also seeing this message in my /var/cron/log file. I have a job that's suppose to run every 5 minutes. I been getting this message in the last few days.

I DON'T have the user account's password set to expire. here's what I have in my /etc/default/passwd file:

#ident "@(#)passwd.dfl 1.392/07/14 SMI"

MAXWEEKS=

MINWEEKS=

PASSLENGTH=6

cron.allow and cron.deny looks fine and the crontab file for the user looks fine. It only started happening recently and nothing was changed prior.

What's really wierd is that as soon as I logged in as the user, the "bad user" message stopped appearing and the cronjob is fine now.

Why did this happen?

dbbyleo at 2007-7-5 17:05:58 >