[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

[Jorge Niedbalski]

I just ran a verification on this package.

root at juju-niedbalski-sec-machine-27:/home/ubuntu# for file in $(strace -e open -i corosync -v 2>&1 | grep -E '.*shm.*' |grep -Po '".*?"'| sed -e s/\"//g); do du -sh $file; done
12K	/dev/shm/qb-corosync-blackbox-header
8.1M	/dev/shm/qb-corosync-blackbox-data

After enabling proposed

root at juju-niedbalski-sec-machine-27:/home/ubuntu# dpkg -l | grep corosync
ii  corosync                         2.3.3-1ubuntu2                   amd64        Standards-based cluster framework (daemon and modules)
ii  libcorosync-common4              2.3.3-1ubuntu2                   amd64        Standards-based cluster framework, common library

root at juju-niedbalski-sec-machine-27:/home/ubuntu# for file in $(strace -e open -i corosync -v 2>&1 | grep -E '.*shm.*' |grep -Po '".*?"'| sed -e s/\"//g); do du -sh $file; done
du: cannot access ‘/dev/shm/qb-corosync-blackbox-header’: No such file or directory
du: cannot access ‘/dev/shm/qb-corosync-blackbox-data’: No such file or directory

So, seems to be fixed.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in 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