Hi,
On Tue, Feb 05, 2008 at 01:05:40PM +0100, Andreas Mock wrote:
> > -----Urspr?ngliche Nachricht-----
> > Von: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] Im Auftrag von
> > Dejan Muhamedagic
> > Gesendet: Dienstag, 5. Februar 2008 12:36
> > An: General Linux-HA mailing list
> > Betreff: Re: [Linux-HA] 32 / 64 Bit
>
>
> Hi Dejan,
>
>
> >
> > If I understand your question correctly, those libraries were
> > moved to the $OCF_ROOT/resource.d/heartbeat/. OCF_ROOT is
> > typically set to /usr/lib/ocf.
> >
> > Does that help?
>
>
> I understood the question the following way:
> If someone develops a RA on his "development" platform he knows
> the currently correct paths to the relevant components.
> But if this developer thinks about making this RA runnable
> on different architectures (32/64bit) or different platforms, he
> doesn't know which parts (e.g. paths) are variable and architecture
> or platform dependent.
>
> So, shall the RA developer try to resolve paths at runtime using
> defined and relyable environment variables? Where are they defined???
>
> Or shall the RA developer send his implementation to you and you will
> extract all absolute paths and replace them by build environment variables?
>
> What is the right procedure?
To source $OCF_ROOT/resource.d/heartbeat/.ocf-shellfuncs which in
turn sources /etc/ha.d/shellfuncs. At the top of the latter shell
script there are a bunch of environment variables set. For
example:
$ grep '^:' /etc/ha.d/shellfuncs
: ${HA_DIR:=/etc/ha.d}
: ${HA_RCDIR:=$HA_DIR/rc.d}
: ${HA_CONFDIR=$HA_DIR/conf}
: ${HA_CF:=$HA_DIR/ha.cf}
: ${HA_VARLIB:=/var/lib/heartbeat}
: ${HA_RSCTMP:=/var/run/heartbeat/rsctmp}
: ${HA_FIFO:=/var/lib/heartbeat/fifo}
: ${HA_BIN:=/usr/lib/heartbeat}
: ${HA_NOARCHBIN:=/usr/share/heartbeat}
...
Cheers,
Dejan
> Best regards
> Andreas Mock
>
> _______________________________________________
> 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
