Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
cat /etc/cron.allow

We have added a user to run their crontab job in CentOS 5.x, still they are not able to run the job. If any thing missing from by us, Please feel free to teacher us.

share|improve this question

You really don't give us much to go on. Things to check.

Check cron is running

/sbin/service crond status
crond (pid  4186) is running...

If it's not then start it

/sbin/service crond start

Get the user to run crontab -l this will list the jobs they have defined. If they don't have any jobs defined then use crontab -e create them.

If they do have jobs defined then check that they should have run already - are you just not waiting long enough, look in the /var/log/cron file.

If the jobs are running but you are not getting your expected output then add &>/tmp/cronjob.out to the end of the crontab entry to capture the output of the job.

share|improve this answer
Lain thanks for your quick reply service crond status running /sbin/service crond status crond (pid 2887) is running... – neolix Feb 23 '12 at 10:42
Anything 'interesting' from the rest of the things to check ? – Iain Feb 23 '12 at 10:58
@Lain do you thing so this file acting funny /etc/security/access.conf – neolix Feb 23 '12 at 11:28
If you have made changes it's possible but by default probably not. – Iain Feb 23 '12 at 12:15

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.