News for hackers. Stuff that matters.
Re:Systemd Wants to Expand to Include a Sudo Replacement by saghm on Tuesday April 30, 2024 @03:52PM (#40215510)
> journalctl supports -f, which by your own account you were already using for tail, so I'm not clear what's worse there

Yeah, this is a bit of an odd complaint. If I were this bothered by having to type those, I'd just make an alias to "journalctl --follow --nopager"` and would have forgotten about it years ago.

Re:Systemd Wants to Expand to Include a Sudo Replacement by mdaniel on Tuesday April 30, 2024 @04:20PM (#40215815)
> I'd just make an alias to "journalctl --follow --nopager"` and would have forgotten about it years ago.

You sure would have forgotten about it when you tried to get onto another machine without the magic set of aliases

I am also prepared for someone to chime in that "log egress tools exist" to move up the Maslow's Hierarchy of Log Needs

Re:Systemd Wants to Expand to Include a Sudo Replacement by stoperaticless on Tuesday April 30, 2024 @04:12PM (#40215734)
Never tried it, but if the complainer wrote: tail -f *.logs

Which involves glob’ing. I assume it allows to monitor several services at the same time.

Can systemd do that?

Re:Systemd Wants to Expand to Include a Sudo Replacement by _flux on Tuesday April 30, 2024 @04:35PM (#40215992)
It's the basic function what journalctl -f does by default: follow the global log all jobs write into. -u etc are for filtering that.
Re:Systemd Wants to Expand to Include a Sudo Replacement by tapoxi on Tuesday April 30, 2024 @04:27PM (#40215882)
Yes, journalctl -u postgres -u redis -f etc
Re:Systemd Wants to Expand to Include a Sudo Replacement by mintplant on Tuesday April 30, 2024 @04:36PM (#40216005)
Or just `journalctl -f` to follow all logs.