> An: "The Pacemaker cluster resource manager"
> Betreff: Re: [Pacemaker] Interval-origin in monitor operations does not work
>
> On 2 May 2014, at 4:55 pm, Andrew Beekhof wrote:
>
> >
> > On 15 Apr 2014, at 4:12 am, Rainer Brestan wrote:
>
Uhr
Von: "Andrew Beekhof"
An: "The Pacemaker cluster resource manager"
Betreff: Re: [Pacemaker] Interval-origin in monitor operations does not work
On 2 May 2014, at 4:55 pm, Andrew Beekhof wrote:
>
> On 15 Apr 2014, at 4:12 am, Rainer Brestan wr
s(crm_time_t * a_time, int extra)
>> ydays = crm_time_leapyear(a_time->years) ? 366 : 365;
>> }
>> - while (a_time->days <= 0) {
>> +while (a_time->days < 0) {
>> a_time->years--;
>> a_time->days += crm_
ime->days < 0) {
> a_time->years--;
> a_time->days += crm_time_leapyear(a_time->years) ? 366 : 365;
> }
>
> Rainer
> Gesendet: Mittwoch, 09. April 2014 um 08:57 Uhr
> Von: "Andrew Beekhof"
> An: "The Pacemaker cluster re
time->years) ? 366 : 365;
}
Rainer
Gesendet: Mittwoch, 09. April 2014 um 08:57 Uhr
Von: "Andrew Beekhof"
An: "The Pacemaker cluster resource manager"
Betreff: Re: [Pacemaker] Interval-origin in monitor operations does not work
On 1 Apr 2014, at 5:10 am, Rainer Brestan wrote
On 1 Apr 2014, at 5:10 am, Rainer Brestan wrote:
> Using interval-origin in monitor operation definition does not work any more.
> Veryfied on Pacemaker 1.1.10, but we think it does not work since 1.1.8 until
> now.
>
> Pengine calculates start delay in function unpack_operation and calls the
