[Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
Rafael David Tinoco
rafaeldtinoco at ubuntu.com
Thu Mar 19 21:30:08 UTC 2020
(c)rafaeldtinoco at 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
DAEMON=/usr/sbin/$NAME
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
-PIDFILE=/var/run/corosync.pid
RARUNDIR=/var/run/resource-agents
# Exit if the package is not installed
If anyone faces this issue, just remove the second PIDFILE as it appears
to be a leftover. I'll fix this and point this out to Debian as it also
faces the same issue. NEVERTHELESS, remember that this issue would only
exist if you are using the "sysv" scripts OR the sysv-generator (making
systemd to control the service through sysv scripts).
All others are probably relying in systemd to start/stop/monitor
corosync daemon (/lib/systemd/system/corosync.service).
--
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions
More information about the Ubuntu-server-bugs
mailing list