Hi Jan,
Good clarification on my ugly systemd unit fix, wrote it a bit too fast
and was so happy to finally track that one down.
Good to know the bug will get notified through this channel, I'd be
happy to provide any details to the maintainers if necessary.
Cheers!
--
Julien Semaan
[email protected] :: +1 (866) 353-6153 *155 ::www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
On 2017-12-14 11:25 AM, Jan Pokorný wrote:
On 14/12/17 10:49 -0500, Julien Semaan wrote:
Great success!
Adding the following line to /usr/lib/systemd/system/pacemaker.service did
it:
After=dbus.service
Note, this is not a proper way for overriding the systemd unit files,
which is rather along the lines:
- make a copy to /etc/systemd/system directory
- edit this copy
- issue systemctl daemon-reload so that this is taken into at all
(which also happens automatically after reboot)
Otherwise your changes are lost say after reinstalling pacemaker.
(FTR, in the same vein, I am proposing similar scheme for resource
agents: https://github.com/ClusterLabs/OCF-spec/issues/5)
Now, the question is, should the unit file shipped in the RPM be adjusted
(currently using CentOS 7), if so, is this the best place to get the message
going, or should I post this to a specific BTS ?
Pacemaker maintainers are reading this so will take care of this
for upstream, you may then want to give a heads up to particular
downstream, giving them the right pointers.
Anyway, the change is seemingly straightfoward, but few things
should be answered/investigated first:
- After=dbus.service or rather After=dbus.socket (or both)?
- mere After=, or combined with other relationship modifying
directives
- Wants=, Requires= ... what's the expected behaviour when
DBus crashes (or is it merely hypothetical because then
whole systemd is in trouble then?)
- should DBus reloads somehow affect pacemaker?
- (insert some other questions that are not currently
coming to mind of rather inexpert person)
_______________________________________________
Users mailing list: [email protected]
http://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
_______________________________________________
Users mailing list: [email protected]
http://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
