The "-d" is added in /etc/default/corosync-notifyd nowadays, and that is
taken care in consideration for the sysv scripts:
start-stop-daemon --start --quiet --exec $DAEMON -- $OPTIONS \
|| return 2
and also for the systemd unit file:
[Service]
EnvironmentFile=-/etc/default/corosync-notifyd
ExecStart=/usr/sbin/corosync-notifyd -f $OPTIONS
Type=notify
Restart=on-failure
PrivateTmp=yes
So I'm marking this as Fix Released.
** Changed in: corosync (Ubuntu)
Status: Triaged => Fix Released
** Changed in: corosync (Ubuntu)
Importance: Undecided => Medium
--
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/1437368
Title:
A DAEMON_ARGS="-d" is missing for the corosync-notifyd init script
Status in corosync package in Ubuntu:
Fix Released
Bug description:
Without a -d option, corosync-notifyd refuses to start with the command
start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd --
But it starts OK with
start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd -- -d
According to the man pages, the -d option should be used in order to
make the corosync-notifyd to send DBUS signals on all events, so it
looks like is *should* present as well
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/1437368/+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
