5 ms·

# journalctl -f _PID=${your_pid} # option 1 # systemctl status ${your_pid} # option 2 [1]: https://www.freedesktop.org/software/systemd/man/latest/jour

# journalctl -f _PID=${your_pid} # option 1 # systemctl status ${your_pid} # option 2 [1]: https://www.freedesktop.org/software/systemd/man/latest/journalctl.html#Examples https://www.freedesktop.org/software/systemd/man/latest/jour... [2]: https://www.freedesktop.org/software/systemd/man/latest/systemctl.html#status%20PATTERN%E2%80%A6%7CPID%E2%80%A6%5D https://www.freedesktop.org/software/systemd/man/latest/syst...

Brian_K_White 2y ago
These absolutely SUCK as answers to that question. They entirely miss the point. They provide a specific answer to a general problem. The problem with systemnd is it assumes that it's possible for all needs to be predicted and accounted for ahead of time. While "look around at directories and files, and grep within them" works after the fact without any special knowledge or tools. The person who wrote the log file did not need to know how someone will maybe try to access it 23 years later on a different OS. It's just a regular file that can be read by anything over any kind of channel on any os. The person finding themselves needing to read the file does not need to have any particular command installed, or installable, or runnable. It does not require the happy path in order to work. I have a joke I always say, often self-deprecating making fun of my own self for the way I do things sometimes, but also when I'm trying to commiserate with a customer so they don't feel intimidated by "the expert" or "the engineer": "37 easy steps!" Every answer that starts with "it's simple, just journalctl ..." is FUCKING 37 easy steps. The very name of the program itself is a trainwreck. journalctl... it takes me 18 seconds just to type it. systemd is great for managing exquisitely washed masses of drone vms. It's utter and complete shit for direct administration, operation, development, debugging, flexibility, or custom integrations.
- throwaway7356 2y ago
  > journalctl... it takes me 18 seconds just to type it. Sounds like you don't use a keyboard often enough to even remember where the keys are. Not sure I would expect deep (or even shallow) knowledge on UNIX system administration from such a person.
- robertlagrant 2y ago
  > These absolutely SUCK as answers to that question. They entirely miss the point. They provide a specific answer to a general problem. No they don't. They are good answers. If you want answers to a more general problem, then ask. This is not an emotive topic.
  - Brian_K_White 2y ago
    They may be correct answers, in that they accomplish a task. They suck in that the proposed method for accomplishing the task is a suck-ass downgrade from the previous ways the new way proposes to displace. I beg to differ about emotive, because absolutely the other side of this fence behaves every bit as butt-hurt when challenged as I just did. You yourself just said these crappy commands were good, as a purely unfounded assertion. They are great because you just say they are great. That is even less objective than my rant. I at least explained what exactly I find so bad. Tell me more about not emotive.
    - robertlagrant 2y ago
      > You yourself just said these crappy commands were good, as a purely unfounded assertion. They are great because you just say they are great. That is even less objective than my rant. I at least explained what exactly I find so bad. Tell me more about not emotive. Very well: I didn't say the commands were good or great. If you attempt a little objectivity you'll see it.
      - Brian_K_White 2y ago
        If you attempt a little objectivity, you will see that addressing the answers (vs the commands) was in my first response. Before even going into the nature of the commands, I said that the answer does not match the question. The answers addressed details, while the details in the question were merely examples. Missing the point is actually merely one of the at least two dimensions along which the answers suck. Thank you for reminding me about that.
        2y ago
- sgarland 2y ago
  Agreed. I’ve tried to get used to it on Debian 12 for personal VMs. I just can’t. I don’t care. grep and awk are always going to be available, and I know how to use them.
- superb_dev 2y ago
  I didn’t answer the general question because I don’t care, I have no dog in this fight. Im just happy to provide information. I like systemd and have found it extremely useful. If it doesn’t fill a need for you then use something else.
- rcxdude 2y ago
  It's way better than the previous status quo: now, more or less whatever distro I'm on, there's one command which answers that question directly, not a process of guessing how this system happens to be set up. You can guess and grep through most any kind of problem, but I don't see why anyone would want to do it as anything but a last resort, and to me that fits '37 easy steps' far more than the 1 consistent step in these replies (notice how none of them say 'oh, but on debian...'?).

Brian_K_White 2y ago

These absolutely SUCK as answers to that question. They entirely miss the point. They provide a specific answer to a general problem. The problem with systemnd is it assumes that it's possible for all needs to be predicted and accounted for ahead of time. While "look around at directories and files, and grep within them" works after the fact without any special knowledge or tools. The person who wrote the log file did not need to know how someone will maybe try to access it 23 years later on a different OS. It's just a regular file that can be read by anything over any kind of channel on any os. The person finding themselves needing to read the file does not need to have any particular command installed, or installable, or runnable. It does not require the happy path in order to work. I have a joke I always say, often self-deprecating making fun of my own self for the way I do things sometimes, but also when I'm trying to commiserate with a customer so they don't feel intimidated by "the expert" or "the engineer": "37 easy steps!" Every answer that starts with "it's simple, just journalctl ..." is FUCKING 37 easy steps. The very name of the program itself is a trainwreck. journalctl... it takes me 18 seconds just to type it. systemd is great for managing exquisitely washed masses of drone vms. It's utter and complete shit for direct administration, operation, development, debugging, flexibility, or custom integrations.

throwaway7356 2y ago
> journalctl... it takes me 18 seconds just to type it. Sounds like you don't use a keyboard often enough to even remember where the keys are. Not sure I would expect deep (or even shallow) knowledge on UNIX system administration from such a person.
robertlagrant 2y ago
> These absolutely SUCK as answers to that question. They entirely miss the point. They provide a specific answer to a general problem. No they don't. They are good answers. If you want answers to a more general problem, then ask. This is not an emotive topic.
- Brian_K_White 2y ago
  They may be correct answers, in that they accomplish a task. They suck in that the proposed method for accomplishing the task is a suck-ass downgrade from the previous ways the new way proposes to displace. I beg to differ about emotive, because absolutely the other side of this fence behaves every bit as butt-hurt when challenged as I just did. You yourself just said these crappy commands were good, as a purely unfounded assertion. They are great because you just say they are great. That is even less objective than my rant. I at least explained what exactly I find so bad. Tell me more about not emotive.
  - robertlagrant 2y ago
    > You yourself just said these crappy commands were good, as a purely unfounded assertion. They are great because you just say they are great. That is even less objective than my rant. I at least explained what exactly I find so bad. Tell me more about not emotive. Very well: I didn't say the commands were good or great. If you attempt a little objectivity you'll see it.
    - Brian_K_White 2y ago
      If you attempt a little objectivity, you will see that addressing the answers (vs the commands) was in my first response. Before even going into the nature of the commands, I said that the answer does not match the question. The answers addressed details, while the details in the question were merely examples. Missing the point is actually merely one of the at least two dimensions along which the answers suck. Thank you for reminding me about that.
      - 2y ago
sgarland 2y ago
Agreed. I’ve tried to get used to it on Debian 12 for personal VMs. I just can’t. I don’t care. grep and awk are always going to be available, and I know how to use them.
superb_dev 2y ago
I didn’t answer the general question because I don’t care, I have no dog in this fight. Im just happy to provide information. I like systemd and have found it extremely useful. If it doesn’t fill a need for you then use something else.
rcxdude 2y ago
It's way better than the previous status quo: now, more or less whatever distro I'm on, there's one command which answers that question directly, not a process of guessing how this system happens to be set up. You can guess and grep through most any kind of problem, but I don't see why anyone would want to do it as anything but a last resort, and to me that fits '37 easy steps' far more than the 1 consistent step in these replies (notice how none of them say 'oh, but on debian...'?).