The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: corosync (Ubuntu Eoan)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is double-defined for the corosync-notifyd init script
Status in corosync package in Ubuntu:
Fix Released
Status in corosync source package in Trusty:
Won't Fix
Status in corosync source package in Xenial:
Triaged
Status in corosync source package in Bionic:
Triaged
Status in corosync source package in Disco:
Won't Fix
Status in corosync source package in Eoan:
Won't Fix
Status in corosync source package in Focal:
Fix Released
Bug description:
A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE:
> PIDFILE=/var/run/$NAME.pid
> SCRIPTNAME=/etc/init.d/$NAME
> PIDFILE=/var/run/corosync.pid
The first one is correct and the second one is wrong as it refers to
the corosync service's pidfile instead
The corosync package version is 2.3.3-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
