search for: next_start

...ompleted by the time the next interval rolls around, will a new thread be started, resulting in 2 threads for the same worker? Looking at start_process, it seems like the thread gets created (which spins off the thread and then continues to execute the start_process method, right?), then sets the @next_start. So if the @next_start is in 10 minutes, but it takes 20 minutes to finish the current work, start_timer will attempt to call start_process on the job, and kick off another thread, resulting in 2 threads. Is this correct? What I want to happen is that the thread can''t get kicked off aga...

...id in your {args} when you queue_job({args}) I''ll attach the files. If they don''t go through, I''ll resend as text. BTW, This works well enough for me, but I''m learning as I go too, so no guarantees :) I don''t use the fancy timing options, so ymmmv for :next_start and :interval. Let me know if you find any issues (though I''m off-line for a week after this post). I''m wondering myself if it might be better to reuse child workers instead of re-spawning new ones. Another day maybe. cheers, David Lemstra -------------- next part --------------...

Hello, i need to have some jobs scheduled in the background and executed at specific times. I wanted to make a worker who does that - and it works a little bit - but i had an enlightment... why not make bgdrb itself play that role? i mean, the MiddleMan has already everything needed! a timer thread, currently used only for deleting old workers and the workers itself. since im not familiar with