Bug 979446

Summary:	RFE: journald: provide API to register a callback for events
Product:	[Fedora] Fedora	Reporter:	Jiri Moskovcak <jmoskovc>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	bnocera, dtardon, johannbg, lnykryn, msekleta, plautrba, systemd-maint, tsmetana, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-13 08:50:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Moskovcak 2013-06-28 14:52:56 UTC

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

Comment 1 Kay Sievers 2013-07-02 15:38:09 UTC

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.

Comment 4 David Tardon 2022-09-13 08:50:38 UTC

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.