Forum: CFEngine Help
Subject: Re: Aborting CFEngine agent if there is an earlier instance of it
already running
Author: sauer
Link to topic: https://cfengine.com/forum/read.php?3,27239,27267#msg-27267
I had no luck with expireafter. As I recall, there was some discussion earlier
about adding a
On Sun, Sep 9, 2012 at 11:08 AM, Marco Marongiu wrote:
> On 07/09/12 13:11, no-re...@cfengine.com wrote:
>> Look at expireafter in agent control.
>
> Hi Neil, all
>
> I see in the reference that expireafter has a default value of 1 minute
> "for time before on-going promise repairs are interrupted
On 07/09/12 13:11, no-re...@cfengine.com wrote:
> Look at expireafter in agent control.
Hi Neil, all
I see in the reference that expireafter has a default value of 1 minute
"for time before on-going promise repairs are interrupted". If it was
effective in Aleksey, he would never have the problem
Forum: CFEngine Help
Subject: Re: Aborting CFEngine agent if there is an earlier instance of it
already running
Author: neilhwatson
Link to topic: https://cfengine.com/forum/read.php?3,27239,27243#msg-27243
Look at expireafter in agent control
Hi Aleksey
I haven't been burnt by this (yet) so you may want to take this with
reservation :)
I'd go for a double approach here. As you say, I'd count root's
instances of cf-agent and use abortclasses to give up if the count is
higher than 1. To be more effective, this check should happen as ear
I noticed that since the agent is started at (short) regular
intervals, if something goes wrong and the previous run doesn't
complete within 5 minutes, the next run will overlap the earlier run.
Again, if the run doesn't finish in time, then I will have 3 runs...
then 4... etc. processes pile up
