3 is the correct choice for several reasons. If the jobs should not
overlap, it's the scripts reponsibility to provide a check and react
accordingly. IMHO Cron should not skip tasks or change the start time
voluntarily (it's not a resource manager). Also, 3 is how the 'real'
cron works.
On Mar 1,
Ah, a possible limitation of implementing option 1 from option 3,
however, would be that the number of threads/processes (depending on
which one is used for the jobs here) would increase linearly during
execution.
Not so bad if exceeding 15 minutes only happens occasionally (and the
task takes a
On Mon, Mar 1, 2010 at 05:03, AchipA attila.cs...@gmail.com wrote:
3 is the correct choice for several reasons. If the jobs should not
overlap, it's the scripts reponsibility to provide a check and react
accordingly. IMHO Cron should not skip tasks or change the start time
voluntarily (it's
3
-Thadeus
On Mon, Mar 1, 2010 at 5:42 AM, Álvaro Justen [Turicas]
alvarojus...@gmail.com wrote:
On Mon, Mar 1, 2010 at 05:03, AchipA attila.cs...@gmail.com wrote:
3 is the correct choice for several reasons. If the jobs should not
overlap, it's the scripts reponsibility to provide a
this is in trunk. Option 3. Please check it.
Mind that if a cron process gets stuck option 3 causes a proliferation
of processes that will eventually crash the machine.
On Mar 1, 9:26 am, Thadeus Burgess thade...@thadeusb.com wrote:
3
-Thadeus
On Mon, Mar 1, 2010 at 5:42 AM, Álvaro Justen
follow up...
one thing is not clear to me. Say a cron job should start every 10
minutes. If the actual execution of the job takes longer (say 15
minutes) what is the right thing to do?
1) Queue them (thus running every 15 minutes but the size of the queue
gets longer and longer)?
2) Skip an extra
6 matches
Mail list logo
