[Linux-HA] Where is BasicSanityCheck?

[Andrew Beekhof]

On Tue, Jul 22, 2008 at 18:12, Michael Alger <linux-ha at mm.quex.org> wrote:
> On Tue, Jul 22, 2008 at 05:25:36PM +0200, Schmidt, Florian wrote:
>> Yeah, that's the question.
>>
>> I don't find it in /usr/lib/heartbeat, nor does
>> find / -name *BasicSanity*
>>
>> rpm -qa|grep heart
>> pacemaker-heartbeat-0.6.1-5.3
>> heartbeat-common-2.1.3-15.1
>> heartbeat-2.1.3-15.1
>> heartbeat-resources-2.1.3-15.1
>>
>> Can anyone tell me how to find it?
>
> Interesting. In the Debian packages it's part of the heartbeat
> package, but after downloading almost all of the SLES10 RPMs I
> discovered that it's in the heartbeat-devel package.
>
> $ rpm -qpl heartbeat-devel-2.1.3-23.1.i586.rpm  | grep -i sanity
> /usr/share/heartbeat/BasicSanityCheck
> /usr/share/heartbeat/stonithdtest/STONITHDBasicSanityCheck
>
>
> As a general question for the Linux-HA devs/package maintainers,
> what are the general recommendations for when and how to update a
> system when using the packages from:
>
> http://download.opensuse.org/repositories/server:/ha-clustering/
>
> Obviously you guys prefer us to run the latest code, but some of us
> subscribe to the "if it ain't broke, don't fix it" credo. i.e. if
> it's working and is stable, leave it as is.  Thoughts?

Now that Pacemaker is no longer part of Heartbeat, CRM development has
been split into two streams (stable and unstable/dev), the packages at
that location are highly likely to be the best we've produced up to
that point in time.  As much as we try to prevent it, occasionally a
regression will slip through, but as a whole they get better and
better (because they're feature frozen).

When you update is entirely up to you and your organization... I
recommend looking through the changelogs to see if there is anything
relevant to your configuration.
Particularly anything labeled with the "High:" prefix (
http://clusterlabs.org/mw/FAQ#What_Do_the_Prefixes_in_Commit_Messages_Mean.3F
)


>
>
> Finally, a more specific question: I'm currently using this package
> from Debian_Etch/i386 @ the above:
>
> 1031100 2008-05-17 02:57 heartbeat_2.1.3-18_i386.deb
>
> Looking at the listing now, the 2.1.3-18 package has a modified date
> of 18-Jul-2008. So I downloaded it again, and get this:
>
> 1031094 2008-07-18 21:37 heartbeat_2.1.3-18_i386.deb
>
> Clearly the file has been modified (slightly), but the version
> number remained the same. Is this a common occurrence? I extracted
> the new .deb but the changelog and changelog.Debian haven't changed.

Not sure what the first number is, but the debian packages also get
rebuilt whenever the rpm .spec file is changed.
Perhaps thats what you're seeing.