Is there a limit to the number of entries in a user's crontab? I have a personal crontab with ~100 entries, and I just added a job to it that does not appear to be running. I can see in syslog when cron launches all the other jobs, but not this last one.
This is ubuntu's default vixie cron.
-
It Depends (tm)
You don't say what operating system or what version of cron you're using so its hard to know for sure.
Did you check "man cron" or "man crond"?
I believe that with some, there is a limit of 256 entries.
A quick test on Solaris suggests that a user is limited to 100 lines (but all entries continue to show up in 'crontab -l').
Why are you asking what the limit is? Starting all of those processes automatically at the same time sounds like potential trouble. :-)
To keep my own sanity I prefer to create cron scripts called Hourly, Daily, Weekly, Monthly. etc.
This allows me to group commands and make sure everything doesn't fire at once.
Depending on your needs, this might be a good solution for you as well.
Dennis Williamson : He said "ubuntu".Dennis Williamson : By the way, your answer is almost verbatim of post #7 here: http://archives.devshed.com/forums/unix-linux-135/how-many-lines-allowed-in-crontab-if-any-373205.htmlFrom KPWINC -
There doesn't appear to be a documented limit to the number of crontab entries allowed. So, short of checking the source code to the specific version you're using, perhaps the BUG entry in the crontab manpage could be helpful:
Although cron requires that each entry in a crontab end in a newline character, neither the crontab command nor the cron daemon will detect this error. Instead, the crontab will appear to load normally. However, the command will never run. The best choice is to ensure that your crontab has a blank line at the end.
From Zayne S Halsall
0 comments:
Post a Comment