Andrei Borzenkov writes: > Not sure I really understand the question. If service cannot run > anyway, you can simply remove it from configuration. You can set > target state to stopped. You can unmanage it. It all depends on what > you are attempting to achieve.
I want pacemaker/corosync to give up automatically after a few failed restarts rather that filling the disk with megabytes of syslog entries. Also, I want to add some delay to the restart attempts so that systemd does not complain about too quick restarts. Now even if the mysql database would become available, the service does not start, because systemd tells that restart attempt by pacemaker/corosync is too quick. -- Juha _______________________________________________ Users mailing list: Users@clusterlabs.org http://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
