Re: [Pacemaker] getnameinfo() vs uname()

2012-08-31 Thread Andrew Beekhof
On Fri, Aug 31, 2012 at 5:55 PM, Lars Marowsky-Bree wrote: > On 2012-08-31T12:43:20, Andrew Beekhof wrote: > >> [1] We will implement equivalent functions for the other cluster types. >> [2] The nodelist section looks something like: >> nodelist { >> node { >> nodeid: 1 >> rin

Re: [Pacemaker] getnameinfo() vs uname()

2012-08-31 Thread Andrew Beekhof
On Fri, Aug 31, 2012 at 5:55 PM, Vladislav Bogdanov wrote: > 31.08.2012 05:43, Andrew Beekhof wrote: >> On Wed, Aug 29, 2012 at 8:57 PM, Vladislav Bogdanov >> wrote: >>> 29.08.2012 13:33, Andrew Beekhof wrote: On Wed, Aug 29, 2012 at 4:22 PM, Vladislav Bogdanov wrote: > Hi, > >

Re: [Pacemaker] getnameinfo() vs uname()

2012-08-31 Thread Vladislav Bogdanov
31.08.2012 05:43, Andrew Beekhof wrote: > On Wed, Aug 29, 2012 at 8:57 PM, Vladislav Bogdanov > wrote: >> 29.08.2012 13:33, Andrew Beekhof wrote: >>> On Wed, Aug 29, 2012 at 4:22 PM, Vladislav Bogdanov >>> wrote: Hi, It looks like pacemaker (current master) >>> >>> "current master"

Re: [Pacemaker] getnameinfo() vs uname()

2012-08-31 Thread Lars Marowsky-Bree
On 2012-08-31T12:43:20, Andrew Beekhof wrote: > [1] We will implement equivalent functions for the other cluster types. > [2] The nodelist section looks something like: > nodelist { > node { > nodeid: 1 > ring0_addr: pcmk-1 > quorum_votes: 1 > } > node { >

Re: [Pacemaker] getnameinfo() vs uname()

2012-08-30 Thread Andrew Beekhof
On Wed, Aug 29, 2012 at 8:57 PM, Vladislav Bogdanov wrote: > 29.08.2012 13:33, Andrew Beekhof wrote: >> On Wed, Aug 29, 2012 at 4:22 PM, Vladislav Bogdanov >> wrote: >>> Hi, >>> >>> It looks like pacemaker (current master) >> >> "current master" changes quite rapidly, could you be specific? > > c

Re: [Pacemaker] getnameinfo() vs uname()

2012-08-29 Thread Vladislav Bogdanov
29.08.2012 13:33, Andrew Beekhof wrote: > On Wed, Aug 29, 2012 at 4:22 PM, Vladislav Bogdanov > wrote: >> Hi, >> >> It looks like pacemaker (current master) > > "current master" changes quite rapidly, could you be specific? c72f5ca > >> does not always work nicely on >> top of corosync2 if one

Re: [Pacemaker] getnameinfo() vs uname()

2012-08-29 Thread Andrew Beekhof
On Wed, Aug 29, 2012 at 4:22 PM, Vladislav Bogdanov wrote: > Hi, > > It looks like pacemaker (current master) "current master" changes quite rapidly, could you be specific? > does not always work nicely on > top of corosync2 if one doesn't have /etc/hosts with all cluster nodes > in it, where sh

[Pacemaker] getnameinfo() vs uname()

2012-08-28 Thread Vladislav Bogdanov
Hi, It looks like pacemaker (current master) does not always work nicely on top of corosync2 if one doesn't have /etc/hosts with all cluster nodes in it, where short form of name goes before the long one (so gethostbyaddr() and getnameinfo() return the short one). I tried to run test cluster with