| Summary: | sys-cluster/pacemaker: add custom stop timeout to init | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | JY <jy454> |
| Component: | Current packages | Assignee: | Gentoo Cluster Team <cluster> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | Keywords: | PATCH |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Deadline: | 2020-12-07 | ||
| Attachments: |
/etc/init.d/pacemaker patch
/etc/init.d/pacemaker patch |
||
Created attachment 439938 [details, diff]
/etc/init.d/pacemaker patch
The actual patch
FWIU, this package has been revived. Please CC treecleaners again if the new 'maintainer' doesn't cope. |
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