siriusmart@lemmy.world to Programmer Humor@lemmy.ml · 6 months agoits still deprecatedlemmy.worldimagemessage-square63fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1imageits still deprecatedlemmy.worldsiriusmart@lemmy.world to Programmer Humor@lemmy.ml · 6 months agomessage-square63fedilink
minus-squareKISSmyOSFeddit@lemmy.worldlinkfedilinkarrow-up0·6 months 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-squarezurohki@aussie.zonelinkfedilinkEnglisharrow-up0·6 months 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.
minus-squarepng@discuss.tchncs.delinkfedilinkarrow-up0·6 months agoThis is such a hard part of learning Linux. “Just look at the logs” Which logs? Where? How?
minus-squareKISSmyOSFeddit@lemmy.worldlinkfedilinkarrow-up0·edit-26 months agojournalctl > logs.txt (don’t actually do this)
minus-squareKISSmyOSFeddit@lemmy.worldlinkfedilinkarrow-up0·6 months agoBy default, it saves all your system logs in a text file, starting from the moment you installed your distro.
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?)
By default, it saves all your system logs in a text file, starting from the moment you installed your distro.