[ClusterLabs] Which shell definitions to include?

Ken Gaillot kgaillot at redhat.com
Tue Jul 23 10:07:22 EDT 2019

On Tue, 2019-07-23 at 08:48 +0200, Ulrich Windl wrote:
> Hi!
> My old RAs include /usr/lib/ocf/resource.d/heartbeat/.ocf-shellfuncs. 
> Recently I discovered /usr/lib/ocf/lib/heartbeat/ocf-shellfuncs.
> (I wonder whether the latter shouldn't be /usr/lib/ocf/ocf-shellfuncs 
> simply)
> So what is the recommended path to use for include? If RAs continue
> to use the old includes, we'll never get rid of the historic paths.

I believe the "lib/heartbeat" location is the newer one, and the dot
file is there for backward compatibility.

> BTW: It's all a bit of a mess, because
> /usr/lib/ocf/resource.d/heartbeat/.ocf-shellfuncs includes parts from
> /usr/lib/ocf/lib/heartbeat (${OCF_ROOT}/lib/heartbeat), actually
> being a symbolic link to /usr/lib/ocf/lib/heartbeat/ocf-shellfuncs.
> In .ocf-directories there are definitions that systemd make somewhat
> obsolete like:
> HA_VARRUN (/var/run)
> HA_VARLOCK (/var/lock/subsys)
> For one directory there is an updated definition:
> HA_RSCTMP (/run/resource-agents)
> HA_RSCTMP_OLD (/var/run/heartbeat/rsctmp)
> It's not that I like all the changes systemd requires, but systemd
> complains about not being able to unmount /var while /var/run or
> /var/lock is being used...

Agreed, it should be a build-time option whether to use /run or
Ken Gaillot <kgaillot at redhat.com>

More information about the Users mailing list