3 Commits

Include renames

Author	SHA1	Message	Date
Lennart Poettering	53fc4c48e7	units: tag all .varlink sockets with the right xattrs ... This also relaxes the inode access modes a bit, in case they were set to 0600: we now set the "r" bit too, i.e. use 0644. This is beneficial since it permits unpriv code to read the xattrs of the entrypoints (which require read access). Note that in order to be able to connect() to a socket inode you need write access, hence this shouldn't compromise security in any way.	2026-06-23 23:10:01 +02:00
Kai Lüke	e48b6fca76	journalctl: order systemd-journalctl.socket after systemd-sysusers ... The socket failed on boot due to a ordering problem caused by systemd-sysusers running later and thus the socket group was still missing. The socket unit can only start when systemd-sysusers created the group. Order the socket after systemd-sysusers.service to have the group available.	2026-02-25 00:15:11 +09:00
Michael Vogt	a109189fab	journalctl: add new varlink read service to get entries ... We already have some varlink support for the journal to perform some actions like `Rotate`. It would be nice to be able to query the journal via varlink too so this commit adds a new varlinkctl based journal service that exposes a single GetEntries() call to retrieve journal entries. Basic filtering is supported and we can expand the API as needed. This is a separate `io.systemd.JournalControl` [1] service from the existing `io.systemd.Journald` to decouple read and write (thanks to Lennart for suggesting this). This also extracts some shared helper so that we do not duplicate code when generating the json or when adding the filters. [1] The name mirrors the bootctl->io.systemd.BootControl naming.	2026-02-21 13:02:38 +01:00