ond argument to splay class - "shift" to mean "once in a 6 hour
> shift". Is this sufficient detail and justification to be considered a
> feature request? (Apologies in advance - I realise this is close to a repeat
> of my previous posting a few days ago).
>
>
s a third possibility in the
second argument to splay class - "shift" to mean "once in a 6 hour shift". Is
this sufficient detail and justification to be considered a feature request?
(Apologies in advance - I realise this is close to a repeat of my previous
posting a few days a
We can look into it if you file a feature request, but I'm not sure it's
desirable. You can still do your updates every 15 mins even though the
agent wakes up every 5 if you set the ifelapsed default to 15 mins or more.
On 27/04/11 23:32, Michael Stevens wrote:
> We conceivably could, there's n
We conceivably could, there's not really a reason other than it doesn't seem
necessary to update that often. I may well change it just to get splayclass
working. Any chance of getting the splayclass interval as a settable parameter?
On Apr 27, 2011, at 11:54 AM, Mark Burgess wrote:
> Ah, I see
Ah, I see what you mean. Sorry. You're right, one has to assume a
resolution to do the hashing. Any reason why you can't up to 5 min
resolution?
On 27/04/11 19:48, Michael Stevens wrote:
> How would I go about having splayclass work with our current */15 run
> interval?
>
> On Apr 26, 2011, at
How would I go about having splayclass work with our current */15 run interval?
On Apr 26, 2011, at 9:20 PM, Mark wrote:
> No nothing is hardcoded, but the default exec time is 5 minutes. You are not
> missing out.
>
>
> Mark
>
>
> On 27 Apr 2011, at 01:09, Michael Stevens wrote:
>
>> I wa
.ncl.ac.uk/
>-Original Message-
>From: help-cfengine-boun...@cfengine.org [mailto:help-cfengine-
>boun...@cfengine.org] On Behalf Of Mark
>Sent: 27 April 2011 05:20
>To: Michael Stevens
>Cc: help-cfengine@cfengine.org
>Subject: Re: Cfengine Help: Re: Avoiding "Duplicate
No nothing is hardcoded, but the default exec time is 5 minutes. You are not
missing out.
Mark
On 27 Apr 2011, at 01:09, Michael Stevens wrote:
> I wasn't aware of this. Correct me if I'm wrong, but from reading the docs,
> the "on" interval is hard-coded to 5 minutes, eg, since we're runni
I wasn't aware of this. Correct me if I'm wrong, but from reading the docs, the
"on" interval is hard-coded to 5 minutes, eg, since we're running cf3 every 15
minutes from cron, we'd miss 2/3 of the activations unless we up our schedule
to every 5 minutes.
On Apr 26, 2011, at 11:19 AM, no-re..
