Results 1 to 5 of 5
I am using redhat FC2, i realised that the crond is always not very stable. Everytime i have to reboot the box in order to get it working after a ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 09-18-2004 #1Just Joined!
- Join Date
- Sep 2004
- Posts
- 9
Cron not working
I am using redhat FC2, i realised that the crond is always not very stable. Everytime i have to reboot the box in order to get it working after a while.
When I entered the following,
crontab schedule.cron
I did a crontab -l, it shows the scheduled job, * * * * * echo "hello".
But i waited for minutes, the 'hello' message never came.
Is this a problem in the FC2 release?
I tried 'kill -9 crond' and restart the crond process. But it didn't work too.
Any suggestions
- 09-18-2004 #2Linux User
- Join Date
- Jul 2004
- Location
- Poland
- Posts
- 368
Hmm... Perhaps the message is redirected to system log or hits a different virtual terminal. What if you tried to:
Will the file be created?Code:* * * * * touch "/tmp/hello"
"I don't know what I'm running from
And I don't know where I'm running to
There's something deep and strange inside of me I see"
- 09-22-2004 #3Just Joined!
- Join Date
- Sep 2004
- Posts
- 9
I think i found the problem why no display on the screen......interesting the messages are sent to my root mailbox.
Don't know why this is the case.
But the cron still works i guess.
- 06-12-2006 #4Just Joined!
- Join Date
- Jun 2006
- Posts
- 1
Crontab not working
Hi all,
i have set up a cron job like this
* * * * * bash -c ulimit -f unlimited
It fails becasue
#200 - System error 12 - Lack of resources (memory, locks, handles, etc). (OS last error:12).
- 06-14-2006 #5Linux User
- Join Date
- Jul 2004
- Location
- Poland
- Posts
- 368
What is the reason to have this line executed every minute by bash? If I guess correctly your intentions, then you are trying to bypass some system restrictions. But even if you are allowed to, then you cron entry seems to be a no-op. It starts a bash, executes ulimit for this bash 'session' and quits the that bash. Only programs that had been spawned from that bash would have been affected by your limits.
Originally Posted by unlv "I don't know what I'm running from
And I don't know where I'm running to
There's something deep and strange inside of me I see"


Reply With Quote
