Eduardo
Thanks for quick response (and really nice tool).
As you proposed, I ended up with two processes, one being based on doit, the other simply changing content of now.txt file once in 60 seconds.
The timeout uptodate function sounds interesting, but I guess, it would take effect only after I would start the doit jobs later on. My current solution (changing now.txt file by external process) has an advantage, that it "kicks" the jobs via "watch" feature (I know, it will start processing not sooner then previous jobs will be completed, this is fine).
Regarding long running task relationship with other ones - logically there is relationship (via now.txt), but technically from doit point of view it is not. There is the contradiction of the task being long running (in other words never finished) and the fact, doit shall at some moment evaluate results of the task (which is probably when it finishes - thus never).
Remaining question: is there an option to use "auto" and let doit use 2 or more processes? In my case the "auto" would schedule processing and "-n 4" would allow to do the processing faster when the time comes.
Alternate solution for me would be to run doit (with "-n 4") in a loop, or within a process being driven by watchdog or similar solution.
cheers