22.02.2012 22:44, Ante Karamatic wrote: > On 22.02.2012 19:45, Vladislav Bogdanov wrote: > >> I looked at that RAexec very early, just after it was commited, and I >> understand that it requires running dbus daemon to operate. I prefer to >> simplify operation chains, so that is really not an option for me to >> rely on one more service to do simple job. > > It never required dbus running. It uses the same API as initctl - > libdbus. dbus daemon has nothing to do with IPC; it's mostly used for > 'broadcasting' hardware changes.
Thanks for clarification, that wasn't clear at the moment I looked at it. If I knew that, I wouldn't write that RA. One remark, my RA has possibility to check service aliveness on monitor operation and repair that service if it hangs. I use it for libvirtd which sometimes become unresponsive so I need to restart it before all other libvirt-related resources begin to fail. Fortunately, modern libvirtd can be restarted without affecting guests. Of course, that is just a hack, and that should be fixed in libvirtd, but we live in a real world... Best, Vladislav _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
