> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag von
> Dejan Muhamedagic
> Gesendet: Dienstag, 5. Februar 2008 14:19
> An: General Linux-HA mailing list
> Betreff: Re: [Linux-HA] 32 / 64 Bit
Hi Dejan,
> > 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}
> ...
1) Does this mean I can rely on $OCF_ROOT being set and on
$OCF_ROOT/resource.d/heartbeat/.ocf-shellfuncs being a shell snippet to
execute that sets the listed variables?
2) Can I rely on these variables to be set now and in future? Is it part
of the RA api?
3) How do I get these environment variables if I need/want to use another
programming language for RA?
4) Who is fiddling with sheebang paths? (Can I assume LSB compliance?)
5) Where do I have to document other dependencies, e.g. certain interpreter?
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
