News for hackers. Stuff that matters.
Re:Systemd Wants to Expand to Include a Sudo Replacement by superb_dev on Tuesday April 30, 2024 @04:11PM (#40215724)
Well `-u` refers to the unit file, so I would start with `sudo systemctl status` which lists the status of active unit files. I bet I could find the unit name I'm looking for there. If not, then `sudo systemctl list-units` should have it. (and you can grep the output of both)

Systemd and Journald are less opaque than I used to think. Even if you don't want to learn the commands, all of its unit files (and the relationships between them) are available through the filesystem. Most of your unit files will be in `/etc/systemd/system`, and the active relationships between units are expressed through soft links.

Re:Systemd Wants to Expand to Include a Sudo Replacement by aeonik on Tuesday April 30, 2024 @07:33PM (#40217753)
How would you exclude certain units from your logs? Let's say that Auditd is spamming your logs, and you just want to exclude those?

Can you filter on search? How do you prevent applications from writing to Systemd at all?

Re:Systemd Wants to Expand to Include a Sudo Replacement by superb_dev on Tuesday April 30, 2024 @11:13PM (#40219117)
I would start with `man systemd`, or maybe `journalctl —help`.

If you don’t want a service to log to systemd, then don’t run it in systemd?

Re:Systemd Wants to Expand to Include a Sudo Replacement by pcthrowaway on Wednesday May 01, 2024 @01:51AM (#40219957)
I think you can also configure the journal per unit right? Don't remember how exactly, at the very least you can stream logs to a different system.

There are also services which will just use their own logging convention for some reason. Honestly it's easier just to go with journalctl for everything you can.

Re:Systemd Wants to Expand to Include a Sudo Replacement by ramses0 on Tuesday April 30, 2024 @09:41PM (#40218606)
systemctl does not have the Unix nature.