From f33c8cffc0789d7544ec29c22fc846b59172af8b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20Pokorn=C3=BD?= Date: Thu, 16 Nov 2017 10:43:46 +0100 Subject: [PATCH] systemd: make sure neither of pacemaker{,_remoted} is process-limited --- lrmd/pacemaker_remote.service.in | 4 +--- mcp/pacemaker.service.in | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/lrmd/pacemaker_remote.service.in b/lrmd/pacemaker_remote.service.in index d5717f6d0..13e7df8f4 100644 --- a/lrmd/pacemaker_remote.service.in +++ b/lrmd/pacemaker_remote.service.in @@ -21,9 +21,7 @@ EnvironmentFile=-@CONFIGDIR@/sbd 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 diff --git a/mcp/pacemaker.service.in b/mcp/pacemaker.service.in index 516de0f82..a2ab96162 100644 --- a/mcp/pacemaker.service.in +++ b/mcp/pacemaker.service.in @@ -41,9 +41,7 @@ SuccessExitStatus=100 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 -- 2.15.0