> Le 16 oct. 2017 à 19:24, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> have a "cron" utility
> a process that has a list (records, array, whatever) of all processes
> that are deamons
> have it wake the deamon as appropriate using Call process.
When the delay is important,
have a "cron" utility
a process that has a list (records, array, whatever) of all processes
that are deamons
have it wake the deamon as appropriate using Call process.
All deamons use Pause Process, rather then delay to sleep.
ex:
Cron:
Repeat
Process count := number of processes to manage
f
Thanks Jim,
It sounds like it almost has to be an integer value...
If there is a limit, it would be nice for the docs to specify what the limit is.
dave
On Mon, Oct 16, 2017 at 10:28 AM, Jim Hays via 4D_Tech
<4d_tech@lists.4d.com> wrote:
> Max delay used to be something like 32000 ticks. (We ha
Max delay used to be something like 32000 ticks. (We have an old //comment
from 2006 that thinks so anyway)
On Mon, Oct 16, 2017 at 12:20 PM, Dave Nasralla via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Hey All,
>
> Ran into an odd issue. Like many of you have have a Cron Daemon to run
> daily tas
Hey All,
Ran into an odd issue. Like many of you have have a Cron Daemon to run
daily tasks. Usually I have it wake up at least once a day.
In one newer system, there was a job that only had to run once a
month. I tried to delay the process for 30 days it is fails - like
does not delay AT ALL.
e
5 matches
Mail list logo