Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 588208 - sys-cluster/pacemaker: add custom stop timeout to init
Summary: sys-cluster/pacemaker: add custom stop timeout to init
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Deadline: 2020-12-07
Assignee: Gentoo Cluster Team
Keywords: PATCH
Depends on:
Reported: 2016-07-07 08:56 UTC by JY
Modified: 2020-12-18 08:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

/etc/init.d/pacemaker patch (pacemaker.initd,952 bytes, patch)
2016-07-07 08:56 UTC, JY
Details | Diff
/etc/init.d/pacemaker patch (pacemaker.patch,536 bytes, patch)
2016-07-07 08:59 UTC, JY
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description JY 2016-07-07 08:56:33 UTC
Created attachment 439936 [details, diff]
/etc/init.d/pacemaker patch

We've been using pacemaker to manage a few apps, but whenever we stop the pacemaker/corosync service, pacemaker tries to stop the managed services first, taking a long time (we're talking about tomcat/pgsql here) and falling into the start-stop-daemon default stop timeout.

Here is a patch to /etc/init.d/pacemaker which allows to set a custom stop timeout using the classic ssd --retry option

Currently using pacemaker-1.1.12-r2
Comment 1 JY 2016-07-07 08:59:00 UTC
Created attachment 439938 [details, diff]
/etc/init.d/pacemaker patch

The actual patch
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2020-12-18 08:50:02 UTC
FWIU, this package has been revived.  Please CC treecleaners again if the new 'maintainer' doesn't cope.