On Tue, Apr 7, 2009 at 6:13 AM, btinsley wrote:
> On Tue, Apr 7, 2009 at 4:44 AM, Andrew Beekhof wrote:
>
>> On Tue, Apr 7, 2009 at 11:39, Dejan Muhamedagic
>> wrote:
>> > On Tue, Apr 07, 2009 at 08:07:27AM +0200, Andrew Beekhof wrote:
>> >> Nothing in pacemaker - but the lrmd could be doing so
On Tue, Apr 7, 2009 at 4:44 AM, Andrew Beekhof wrote:
> On Tue, Apr 7, 2009 at 11:39, Dejan Muhamedagic
> wrote:
> > On Tue, Apr 07, 2009 at 08:07:27AM +0200, Andrew Beekhof wrote:
> >> Nothing in pacemaker - but the lrmd could be doing something that may
> >> be involved
> >
> > AFAIK, it doesn
On Tue, Apr 7, 2009 at 11:39, Dejan Muhamedagic wrote:
> On Tue, Apr 07, 2009 at 08:07:27AM +0200, Andrew Beekhof wrote:
>> Nothing in pacemaker - but the lrmd could be doing something that may
>> be involved
>
> AFAIK, it doesn't.
Ok, I was just thinking that its the one that ultimately spawns t
Hi,
On Mon, Apr 06, 2009 at 07:21:44PM -0500, btinsley wrote:
> This is a little early in investigation on my end, but is there anything
> that Pacemaker... or potentially OpenAIS, does that would restrict a cluster
> resource from setting the scheduler type and/or priority? I have been
> tinkerin
On Tue, Apr 07, 2009 at 08:07:27AM +0200, Andrew Beekhof wrote:
> Nothing in pacemaker - but the lrmd could be doing something that may
> be involved
AFAIK, it doesn't.
>
> On Tue, Apr 7, 2009 at 02:21, btinsley wrote:
> > This is a little early in investigation on my end, but is there anything
