4 ms·

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.

amaterasu 3y ago
In which shell?
- ac29 3y ago
  Works in fish, I'll have to remember that one
- alright2565 3y ago
  bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completion https://github.com/systemd/systemd/tree/main/shell-completio...
foxhill 3y ago
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.
- tadfisher 2y ago
  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.
  - foxhill 2y ago
    fair enough :) apologies!
vbezhenar 3y ago
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.

amaterasu 3y ago

In which shell?

ac29 3y ago
Works in fish, I'll have to remember that one
alright2565 3y ago
bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completion https://github.com/systemd/systemd/tree/main/shell-completio...

foxhill 3y ago

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.

tadfisher 2y ago
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.
- foxhill 2y ago
  fair enough :) apologies!

vbezhenar 3y ago

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.