On Tue, Jan 17, 2012 at 06:50:23AM +1100, Andrew Beekhof wrote:
> On Tue, Jan 17, 2012 at 4:56 AM, Dejan Muhamedagic <[email protected]> 
> wrote:
> > On Mon, Jan 16, 2012 at 06:47:54PM +0300, Vladislav Bogdanov wrote:
> >> Hi Dejan,
> >>
> >> thank you very much for a good pointer, you saved me much time.
> >>
> >> 16.01.2012 16:20, Dejan Muhamedagic wrote:
> >> > Hi Vladislav,
> >> >
> >> > On Mon, Jan 16, 2012 at 02:14:29PM +0300, Vladislav Bogdanov wrote:
> >> >> Hi Dejan,
> >> >>
> >> >> I'm evaluating crmsh in place of pacemaker bundled crm (because of
> >> >> rsc_ticket support).
> >> >>
> >> >> With current crmsh (b4b063507de0) it is impossible (ok, very hard) to
> >> >> manage cluster properties:
> >> >> # crm configure
> >> >> crm(live)configure# property [tab] ERROR: crmd:metadata: could not parse
> >> >> meta-data:
> >> >> ERROR: crmd:metadata: could not parse meta-data:
> >> >> ERROR: crmd:metadata: could not parse meta-data:
> >> >> ERROR: crmd:metadata: could not parse meta-data:
> >> >>
> >> >> Every subsequent [tab] press results in two more such lines printed.
> >> >> The same is after changing properties with crm configure edit.
> >> >
> >> > How did you build crmsh? In particular, is this thing properly
> >> > replaced by autofoo:
> >> >
> >> >     crm_daemon_dir = "@GLUE_DAEMON_DIR@"
> >>
> >> It was /usr/lib64/heartbeat while my build of pacemaker already has
> >> daemons installed in /usr/libexec/pacemaker (actually it is built from
> >> master branch of Andrews' private repo).
> >
> > OK, that's bleeding edge source and pacemaker daemons were moved
> > in the meantime. I'll make the error message more specific.
> >
> >> Following patch solved the issue for me
> >>
> >> --- a/configure.ac      2012-01-12 14:32:47.000000000 +0000
> >> +++ b/configure.ac      2012-01-16 15:39:03.413650410 +0000
> >> @@ -187,8 +187,8 @@
> >>  AC_SUBST(CRM_CONFIG_DIR)
> >>
> >>  dnl Eventually move out of the heartbeat dir tree and create
> >> compatability code
> >> -dnl CRM_DAEMON_DIR=$libdir/pacemaker
> >> -GLUE_DAEMON_DIR=`extract_header_define $GLUE_HEADER GLUE_DAEMON_DIR`
> >> +GLUE_DAEMON_DIR=${libexecdir}/pacemaker
> >> +dnl GLUE_DAEMON_DIR=`extract_header_define $GLUE_HEADER GLUE_DAEMON_DIR`
> >>  AC_DEFINE_UNQUOTED(GLUE_DAEMON_DIR,"$GLUE_DAEMON_DIR", Location for
> >> Pacemaker daemons)
> >>  AC_SUBST(GLUE_DAEMON_DIR)
> >
> > Not the correct way, i.e. we should introduce CRM_DAEMON_DIR and
> > then extract the right location from the Pacemaker include file.
> 
> Or you can get it out of pkg-config

Missed that one.
Very good.
Thanks,

Dejan

> > Got the point however :)
> >
> >> Thank you again very much,
> >
> > Welcome!
> >
> > Cheers,
> >
> > Dejan
> >
> >> Vladislav
> >>
> >> _______________________________________________
> >> Linux-HA mailing list
> >> [email protected]
> >> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> >> See also: http://linux-ha.org/ReportingProblems
> > _______________________________________________
> > Linux-HA mailing list
> > [email protected]
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to