A DAEMON_ARGS="-d" is missing for the corosync-notifyd init script
Bug #1437368 reported by
Bogdan Dobrelya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
corosync (Ubuntu) |
Fix Released
|
Medium
|
Rafael David Tinoco |
Bug Description
Without a -d option, corosync-notifyd refuses to start with the command
start-stop-daemon --verbose --start --exec /usr/sbin/
But it starts OK with
start-stop-daemon --verbose --start --exec /usr/sbin/
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
tags: | added: trusty |
description: | updated |
Changed in corosync (Ubuntu): | |
status: | New → Triaged |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
tags: | added: ubuntu-ha |
To post a comment you must log in.
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] =-/etc/ default/ corosync- notifyd /usr/sbin/ corosync- notifyd -f $OPTIONS
EnvironmentFile
ExecStart=
Type=notify
Restart=on-failure
PrivateTmp=yes
So I'm marking this as Fix Released.