Those fixes are already included in corosync v2.3.4: $ git tag --contains cc80c8567d6eec1d136f9e85d2f8dfb957337eef v2.3.4 v2.3.5 $ git tag --contains 384760cb670836dc37e243f594612c6e68f44351 v2.3.4 v2.3.5 $ git tag --contains dfaca4b10a005681230a81e229384b6cd239b4f6 v2.3.4 v2.3.5
inaddy@lp1530837trusty(corosync)$ rmadison corosync corosync | 1.4.2-2 | precise corosync | 1.4.2-2ubuntu0.2 | precise-updates corosync | 2.3.3-1ubuntu1 | trusty corosync | 2.3.4-0ubuntu1 | vivid corosync | 2.3.4-0ubuntu1 | wily corosync | 2.3.4-0ubuntu1 | xenial corosync | 2.3.5-3 | xenial-proposed Thus.. only Trusty needs the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530837 Title: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
