News for hackers. Stuff that matters.
Re:Systemd Wants to Expand to Include a Sudo Replacement by tadfisher on Tuesday April 30, 2024 @04:48PM (#40216154)

    journalctl -f -u <TAB>
Shows you all installed units if you have working shell completion, or 'a<TAB>' gets you all units starting with 'a', etc.
Re:Systemd Wants to Expand to Include a Sudo Replacement by amaterasu on Tuesday April 30, 2024 @07:03PM (#40217538)
In which shell?
Re:Systemd Wants to Expand to Include a Sudo Replacement by ac29 on Tuesday April 30, 2024 @08:01PM (#40217978)
Works in fish, I'll have to remember that one
Re:Systemd Wants to Expand to Include a Sudo Replacement by alright2565 on Tuesday April 30, 2024 @08:40PM (#40218228)
Re:Systemd Wants to Expand to Include a Sudo Replacement by foxhill on Wednesday May 01, 2024 @05:39AM (#40221208)
correct me if i’m wrong, but i believe the point that is trying to be made is;

a system user/admin has an intuition about files. saying that ‘journalctl -f -u’ (fu, indeed :) and whatever else is inherently undiscoverable, and is a.. basically orthogonal mechanism for handling what should be a simple task. i.e., viewing some logs. it’s far easier to compose and extend from files (what if i only care about the mtime of the log, for instance), than this.

look, i think systemd isn’t.. terrible. i also think it’s suffered a bit of complexity fetishisation, and it seems as though that this resulting complexity may have become invisible to you.

run0 doesn’t seem like a bad idea. but i am wincing a bit at the thought of unrestricted javascript determining access control.

Re:Systemd Wants to Expand to Include a Sudo Replacement by tadfisher on Thursday May 02, 2024 @01:10PM (#40238624)
I think you have me confused with someone who cares about the difference between binary and text logs. I have no pony in this race; my comment was just made to help.
Re:Systemd Wants to Expand to Include a Sudo Replacement by foxhill on Thursday May 02, 2024 @06:38PM (#40242150)
fair enough :) apologies!
Re:Systemd Wants to Expand to Include a Sudo Replacement by vbezhenar on Wednesday May 01, 2024 @06:59AM (#40221683)
With `ls -l` I can see file modification dates. How do I do it with journalctl? And why do I need to that that in the first place?

Journald would be perfect if I didn't have to know a thing about it. Work in background, move stuff from stdin/stdout to /var/log/journald/service.log, move old stuff in /var/log/journald/archive/service/2024-04/15.log.gz. I'd be happy. Why do I need this cryptic CLI I don't understand. It brings nothing but pain.