![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| HP-UX HP-UX (Hewlett Packard UniX) is Hewlett-Packard's proprietary implementation of the Unix operating system, based on System V. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| cron job starts new cron proccess | ron76 | SUN Solaris | 3 | 05-11-2008 10:07 PM |
| AIX and cron logs filtering ?: /etc/cronlog.conf, /var/adm/cron/log | Keith Johnson | AIX | 0 | 01-09-2008 05:32 PM |
| cron execution | rameek20 | SUN Solaris | 6 | 10-22-2007 02:30 AM |
| why read line skips some lines... | bluemoon1 | Shell Programming and Scripting | 8 | 10-07-2007 12:55 PM |
| Sequential execution of job in cron | pankajkrmishra | Shell Programming and Scripting | 3 | 08-15-2006 02:19 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
Hi All,
I got a very strange problem, i have created a cron schedule that will run a programme once in every 12 mins, like 04,16,28,40,52 * * * * /myf/startProcessA 1> &- Some time the cron skips the execution such as 04,28 instead of executing at 16 mins. it starts execution at 28, i suspect it may be a cron related problem. Can anybody help me in this regard Thanks Nag |
| Forum Sponsor | ||
|
|
|
#2
|
|||
|
|||
|
Have you tried with another script using the same cron schedule, let's say something very simple. Maybe this doesn't have anything to do with cron. It could be something in your script, difficult to tell without seeing your script.
|
|
#3
|
|||
|
|||
|
Thanks for your reply, the cron script is having more than 100 schedule entries (scripts), the cron execution skips occassionaly (i could not find out when the process will skip).
I have tried to execute the same script with another cron with less number of schedules (15) , then no problem in execution (means no skips) Is there any limitation on the "No. of schedules" of cron???? Last edited by nag_sundaram; 09-13-2005 at 04:33 AM. Reason: More Info |
|
#4
|
||||
|
||||
|
cron does have a limit of how many jobs it can run at one time (100 executing jobs is the limit on Solaris). Just because you have 100 different entries does not mean you have reached that limit unless each one runs every minute.
Check your cron log for errors - possibly /var/cron/log. The only times I have seen issues with it was when a user changed their script and caused it to run longer than needed - cron reached it's limit and the user blamed cron instead of noting that he had over 100 jobs running on the server of the same script. |
|
#5
|
|||
|
|||
|
Quote:
Hi, Can u provide me a link where I can find more infromation on solaris limit of 100 Jobs.... Thanks for this valuable info |
|
#6
|
||||
|
||||
|
See "man queuedefs".
|
|
#7
|
|||
|
|||
|
Quote:
|
|||
| Google The UNIX and Linux Forums |