Description of problem: The current journald API doesn't seem to provide a way to register a callback to events, so the only way to detect a new crash is to poll the journald which feels wrong - the polling is wrong and ABRT should react to the crash immediately, it also saves some data from /proc/<pid> which should be also somehow accessible when we give up the core_pattern hook to journald. Version-Release number of selected component (if applicable): systemd-204-8.fc19.x86_64 Actual results: Can't use journald core collection functionality without loosing features Expected results: Seamless transition to journald without loosing functionality Additional info: has been requested quite some time ago: https://fedorahosted.org/abrt/ticket/849 https://github.com/abrt/abrt/issues/548 https://bugs.freedesktop.org/show_bug.cgi?id=54288
It is planned that messages carrying: MESSAGE_ID=<128 bit uuid> are able to "activate" services. It's not entirely trivial to implement that, so it might take a while until we get to it, considering the long TODO list we have at the moment. It is in any case something that sounds useful and which we want for our own stuff too, it's just not available or implemented at this moment in time.
Fedora is not the place where systemd development is happening. Please report your enhancement request to https://github.com/systemd/systemd/issues . Thank you for understanding.