@[email protected] to Programmer [email protected] • 1 month agoits still deprecatedlemmy.worldimagemessage-square57fedilinkarrow-up11.16Karrow-down127
arrow-up11.14Karrow-down1imageits still deprecatedlemmy.world@[email protected] to Programmer [email protected] • 1 month agomessage-square57fedilink
minus-square@[email protected]linkfedilink20•1 month agoTo be fair, people who know which logs to attach and how to get them usually already know enough to troubleshoot the issue by themselves.
minus-square@[email protected]linkfedilink15•1 month agoThis is such a hard part of learning Linux. “Just look at the logs” Which logs? Where? How?
minus-square@[email protected]linkfedilink4•edit-21 month agojournalctl > logs.txt (don’t actually do this)
minus-square@[email protected]linkfedilinkEnglish4•1 month agoYou’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.
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.
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?)
deleted by creator
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.