Re: [ClusterLabs] Which shell definitions to include?
On 23/07/19 09:07 -0500, Ken Gaillot wrote: > On Tue, 2019-07-23 at 08:48 +0200, Ulrich Windl wrote: >> 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 > /var/run Sounds more like a distro systemic inconsistency, since when /var/run and /var/lock are just symlinks to /run-rooted counterparts (is it your case?), it suggests a hint that /var shall never be unmounted prior to /run itself (at which point the still surviving daemons will be in troubles equally and the ordering hence doesn't sit well for these for some reason -- I am assuming the only use case here is a system shutdown). I think I'd pay attention to other parts of the system or customized configuration if you are seeing problems like mentioned above; feels orthogonal to which access path for the same effective location resource-agents project uses. /me wonders, was it a deliberate design step from systemd? -- Jan (Poki) pgpS0GNCA4tjQ.pgp Description: PGP signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Which shell definitions to include?
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 /var/run -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] Which shell definitions to include?
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. 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... Regards, Ulrich ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/