On 3/21/18 1:51 PM, Wolfgang Link wrote:
>
>> So does this mean that all those processes are sitting in a "queue" waiting
>> to execute? wouldn't it be more sensible for the script to terminate if a
>> process is already running for the same job?
>>
> No because as I wrote 15 is default, but we
> So does this mean that all those processes are sitting in a "queue" waiting
> to execute? wouldn't it be more sensible for the script to terminate if a
> process is already running for the same job?
>
No because as I wrote 15 is default, but we have many user which have longer
intervals like
Hi Wolfgang,
So does this mean that all those processes are sitting in a "queue" waiting
to execute? wouldn't it be more sensible for the script to terminate if a
process is already running for the same job?
Regards,
Mark
On 21 March 2018 at 12:40, Wolfgang Link wrote:
>
Hi,
this indicates that the sync time is to low.
cron fork every (default) 15 minutes a pve-zsync process.
If the former pve-zsync process is not finished, it will wait until the former
process is done.
You should rise your sync interval this can be done in the
/etc/cron.d/pve-zsync.
Best
Hi All,
I've been using pve-zsync for a few months - it seems to work pretty well.
However, I have just noticed it doesn't seem to be terminating itself
correctly. at present I have around 800 pve-zsync processes (sleeping)
which all seems to be duplicates. (I would expect 1 per VMID?)
Has