BUG: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622
PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is double-defined for the corosync-notifyd init script
To manage notifications
(c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ git diff HEAD
diff --git a/debian/corosync-notifyd.init b/debian/corosync-notifyd.init
index c908618..837e48a 100644
--- a/debian/corosync-notifyd.init
+++ b/debian/corosync-notifyd.init
@@ -21,7 +21,6 @@ NAME=corosync-notifyd
Okay, this is a very simple fix but it is tricky... mainly because ..
possibly 99% of the users of this package are using systemd and the
corosync service unit file... which does not face this issue. I'm not
entirely sure a SRU is the right thing to do on all affected Ubuntu
versions (Xenial,
** Also affects: corosync (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Focal)
Importance: Undecided
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Triaged
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
