On 2008-02-05T14:55:35, Andreas Mock <[EMAIL PROTECTED]> wrote:
> 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?
Yes, OCF_ROOT is a OCF-mandated setting. The .ocf-shellfuncs might not
be present if the RA is copied to another OCF-compliant system, but for
scripts right now this is a safe assumption and we'll take care to
resolve it going forward for the joint stack.
> 2) Can I rely on these variables to be set now and in future? Is it part
> of the RA api?
No. OCF_ROOT is part of it, but the variables in the shell are a
heartbeat/CRM/Pacemaker "extension". We reserve the right to redefine
them as needed, they are not part of our exported API. However, we will
fix up the scripts included with the package, of course - which is a
long and complicated way of saying one should get their scripts merged
;-)
> 3) How do I get these environment variables if I need/want to use another
> programming language for RA?
That would depend on the language, no? ;-)
>
> 4) Who is fiddling with sheebang paths? (Can I assume LSB compliance?)
LSB compliance should be a given, I hope.
> 5) Where do I have to document other dependencies, e.g. certain interpreter?
In the package dependencies?
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
