pacemaker/bug-1028138_pacemaker-pacemaker.service-TasksMax.patch

27 lines
1.2 KiB
Diff
Raw Normal View History

Index: pacemaker-1.1.18+20171114.f36ad3647/mcp/pacemaker.service.in
===================================================================
--- pacemaker-1.1.18+20171114.f36ad3647.orig/mcp/pacemaker.service.in
+++ pacemaker-1.1.18+20171114.f36ad3647/mcp/pacemaker.service.in
@@ -43,7 +43,7 @@ ExecStart=@sbindir@/pacemakerd -f
# Uncomment TasksMax if your systemd version supports it.
# Only systemd v227 and above support this option.
-#TasksMax=infinity
+TasksMax=infinity
# If pacemakerd doesn't stop, it's probably waiting on a cluster
# resource. Sending -KILL will just get the node fenced
Index: pacemaker-1.1.18+20171114.f36ad3647/lrmd/pacemaker_remote.service.in
===================================================================
--- pacemaker-1.1.18+20171114.f36ad3647.orig/lrmd/pacemaker_remote.service.in
+++ pacemaker-1.1.18+20171114.f36ad3647/lrmd/pacemaker_remote.service.in
@@ -23,7 +23,7 @@ ExecStart=@sbindir@/pacemaker_remoted
# Uncomment TasksMax if your systemd version supports it.
# Only systemd v227 and above support this option.
-#TasksMax=infinity
+TasksMax=infinity
# Pacemaker Remote can exit only after all managed services have shut down;
# an HA database could conceivably take even longer than this