Activity log for bug #1437368

Date Who What changed Old value New value Message
2015-03-27 14:47:31 Bogdan Dobrelya bug added bug
2015-03-27 14:47:44 Bogdan Dobrelya bug added subscriber Thomas Goirand
2015-03-27 14:48:03 Bogdan Dobrelya tags trusty
2015-03-27 14:50:49 Bogdan Dobrelya 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 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
2019-07-04 03:24:07 Rafael David Tinoco corosync (Ubuntu): status New Triaged
2019-07-04 03:24:09 Rafael David Tinoco corosync (Ubuntu): assignee Rafael David Tinoco (rafaeldtinoco)
2019-07-04 03:24:14 Rafael David Tinoco tags trusty trusty ubuntu-ha
2019-07-04 03:51:58 Rafael David Tinoco corosync (Ubuntu): status Triaged Fix Released
2019-07-04 03:52:02 Rafael David Tinoco corosync (Ubuntu): importance Undecided Medium