Pacemaker redesign possibilities

More a scratchpad page at this stage.

Intended for indetifying and long-term fixing of

1. master supervision vs. upgraded daemon binaries in the meantime
Flaw settings: Pacemaker master process,  will try to restart any auxiliary daemon when its non-bailing-out failure is detected. What's not accounted, however, is the situation daemon's binary has been updated in the meantime, meaning the version consistency is possibly broken -- inter-daemon API + assumptions are not guaranteed to be stable, for the most part, it's a private thing for given release.

Possible solutions, either:


 * make initial protocol interchange some version numbers


 * make  check the version string for the daemon in question first


 * remember checksum of the binary when run for the first time, then recheck first


 * RPM only: make installation  (generally, must be volatile memory storage), then   will check that file prior to re-executing any daemon; at the startup, it would ensure that file is not present