this post was submitted on 21 May 2024
1165 points (97.8% liked)
Programmer Humor
32490 readers
506 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I know whenever I try to help someone with a Linux issue it's always an uphill battle to get them to stop guessing what they think the problem might be and show me the logs.
People really don't want to give you the information you need to help them.
I make sure to give my guess and also append as many logs and exact information as possible, right down to every step I took that produced the problem.
So far my success rate with the forums is 0%. But hey, people at least tried to be helpful!
To be fair, people who know which logs to attach and how to get them usually already know enough to troubleshoot the issue by themselves.
You'd think so, but the logs often contain a ton of noise along with the one line that tells me what the actual issue is.
This is such a hard part of learning Linux. "Just look at the logs" Which logs? Where? How?
journalctl > logs.txt(don't actually do this)(what does this do?)