Bug 979446 - RFE: journald: provide API to register a callback for events
Summary: RFE: journald: provide API to register a callback for events
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-28 14:52 UTC by Jiri Moskovcak
Modified: 2022-09-13 08:50 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-09-13 08:50:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.