I was using latest master within witherspoon QEMU. I pulled in the recent patch to enable core dumps.
First I noticed that the, core dump service seems to start before the core directory is created.
Feb 05 17:59:47 witherspoon systemd[1]: Condition check resulted in Phosphor Dump core monitor. being skipped.
Feb 05 18:31:07 witherspoon systemd[1]: Started Phosphor Dump core monitor..
I was running some tests that were generating core dumps, so before I noticed the above, I generated a few core dumps. Once I noticed I restarted the service.
systemctl restart obmc-dump-monitor.service
But I noticed this does not clean out the existing core dumps out in /var/lib/systemd/coredump/.
I think there may be two bugs here, a dependency issue between obmc-dump-monitor.service and whatever creates that directory and the obmc-dump-monitor should clean out any existing core files in /var/lib/systemd/coredump/ on startup.
I was using latest master within witherspoon QEMU. I pulled in the recent patch to enable core dumps.
First I noticed that the, core dump service seems to start before the core directory is created.
I was running some tests that were generating core dumps, so before I noticed the above, I generated a few core dumps. Once I noticed I restarted the service.
But I noticed this does not clean out the existing core dumps out in /var/lib/systemd/coredump/.
I think there may be two bugs here, a dependency issue between obmc-dump-monitor.service and whatever creates that directory and the obmc-dump-monitor should clean out any existing core files in /var/lib/systemd/coredump/ on startup.