siriusmart@lemmy.world to Programmer Humor@lemmy.ml · 2 年前its still deprecatedlemmy.worldexternal-linkmessage-square63fedilinkarrow-up11.18Karrow-down127
arrow-up11.16Karrow-down1external-linkits still deprecatedlemmy.worldsiriusmart@lemmy.world to Programmer Humor@lemmy.ml · 2 年前message-square63fedilink
minus-squareKISSmyOSFeddit@lemmy.worldlinkfedilinkarrow-up21·2 年前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.
minus-squarepng@discuss.tchncs.delinkfedilinkarrow-up16·2 年前This is such a hard part of learning Linux. “Just look at the logs” Which logs? Where? How?
minus-squareKISSmyOSFeddit@lemmy.worldlinkfedilinkarrow-up5·edit-22 年前journalctl > logs.txt (don’t actually do this)
minus-squarezurohki@aussie.zonelinkfedilinkEnglisharrow-up4·2 年前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.
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.