On 14/06/2013, at 7:59 AM, David Vossel <[email protected]> wrote:

> Hey,
> 
> Andrew and I have been running into some inconsistencies between 
> resource-agent packages that we need to get cleared up.
> 
> There's an ocf variable, HA_RSCTMP, used in many of the resource agents that 
> represents a place the agent's can store their PID files and other temporary 
> data.  This data needs to live under some directory in /var/run as that 
> directory is typically cleared on startup.  This is important to prevent 
> stale PID files and other transient data from being persistent across 
> restarts.
> 
> Anyway.  Here's the problem.
> 
> Pacemaker thinks that data should live in '/var/run/heartbeat/rsctmp', but 
> not all the resource-agent packages are consistent with that.  For example, 
> Suse's resource-agent package sets HA_RSCTMP to '/var/run/resource-agents' ( 
> looking at this rpm, 
> http://download.opensuse.org/distribution/11.4/repo/oss/suse/x86_64/resource-agents-1.0.3-9.12.1.x86_64.rpm
>  )
> 
> We need to come to some sort of agreement because ultimately Pacemaker needs 
> to make sure this directory exists on startup, whatever it is.  If pacemaker 
> doesn't create the right directory, it's possible the resource agents won't 
> be able to access it since /var/run is re-initialized on startup.
> 
> so,
> HA_RSCTMP = /var/run/heartbeat/rsctmp
> or
> HA_RSCTMP = /var/run/resource-agents
> 
> thoughts?

It turns out this is entirely a problem of Red Hat's own making.
For some reason our spec file overrides the upstream value that was implemented 
as part of https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2378

Apparently I forgot my part of that conversation.

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to