Run0, a systemd based alternative to sudo, announced

Post by ciupicri » Tue, Apr 30, 2024, 8:22 PM UTC

rangerelf wrote: post #260

superb_dev wrote: post #235

Earlier quoted context omitted.

The follow argument is identical to tail `-f`. `sudo journalctl -f -u `

And what would be the equivalent to, "Oh, I don´t know the name of the log for this process I can see in 'ps aux', let me cd into /var/log and see what filenames I can find ... or grep everything until I can find a couple of words that make some sense so I can keep digging further"? The lack of explorability in journalctl, the "need" to keep everything locked behind their own flavor of tools and magic file types, is…

    # journalctl -f _PID=${your_pid}  # option 1
    # systemctl status ${your_pid}    # option 2

Post by tapoxi » Tue, Apr 30, 2024, 8:26 PM UTC

cogman10 wrote: post #300

lolinder wrote: post #249

Earlier quoted context omitted.

> I could `tail -f *.logs`. I remember how I didn't need to remember about `--no-pager` and `--follow`. journalctl supports -f, which by your own account you were already using for tail, so I'm not clear what's worse there. > I remember how I didn't have to google how to find logs between 10 days ago and 4 days ago, because the logs would be in a .tar created by logrotate with a date in the filename. My memory of thi…

I think my biggest gripe with journalctl is (and this may just be because I'm novice at using it) that discovering what sort of logs are on the system feels a lot more complex. With regular logs, I can go to /var/log, ls the dir, and get a nice list of what's being logged. There will be, for example, an `apache.log` file that has all the logs relevant to apache.

Post by tapoxi » Tue, Apr 30, 2024, 8:27 PM UTC

stoperaticless wrote: post #298

saghm wrote: post #278

Earlier quoted context omitted.

> 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.

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?

Post by [deleted] » Tue, Apr 30, 2024, 8:28 PM UTC

superb_dev wrote: post #235

agilob wrote: post #230

Earlier quoted context omitted.

> remember when you had to write bash scripts to start, stop, restart services This was a really big pain, yes, but I also remember how I could `tail -f *.logs`. I remember how I didn't need to remember about `--no-pager` and `--follow`. I knew where the files were, what they were called. I remember how I didn't have to google how to find logs between 10 days ago and 4 days ago, because the logs would be in a .tar cr…

The follow argument is identical to tail `-f`. `sudo journalctl -f -u `

Post by cogman10 » Tue, Apr 30, 2024, 8:30 PM UTC

tapoxi wrote: post #313

cogman10 wrote: post #300

Earlier quoted context omitted.

I think my biggest gripe with journalctl is (and this may just be because I'm novice at using it) that discovering what sort of logs are on the system feels a lot more complex. With regular logs, I can go to /var/log, ls the dir, and get a nice list of what's being logged. There will be, for example, an `apache.log` file that has all the logs relevant to apache.

It's just journalctl -u apache -f, assuming your distribution calls the unit file "apache", and the last few messages of the logfile appear with systemctl status apache And you don't need to worry about "is this service rotating logs appropriately?"