shark_byte@lemmy.zip to Programmer Humor@programming.dev · 19 hours agoLinux Catlemmy.zipexternal-linkmessage-square50linkfedilinkarrow-up1351arrow-down17file-text
arrow-up1344arrow-down1external-linkLinux Catlemmy.zipshark_byte@lemmy.zip to Programmer Humor@programming.dev · 19 hours agomessage-square50linkfedilinkfile-text
minus-squarerumba@lemmy.ziplinkfedilinkEnglisharrow-up1·5 hours agoReverse chronological order, mostly tac log.txt |head # would give you newest first no good for sort because sort already supports -r no need it for tail on large files because tail already skips to the end. I do a lot of impromptu bash to sus crap out of logs. when you’re balls deep in cat log|grep -v foo| rev|cut -f 1-3 -d \ | |rev Sometimes tac comes in clutch.
minus-squareSprocketfree@sh.itjust.workslinkfedilinkEnglisharrow-up2·2 hours agoThat’s fair. I’d usually just use less and drop to the end. My use cases would always need the older log before a newer log though because that’s the start of the problem. At least that’s how I operate.
Reverse chronological order, mostly
tac log.txt |head # would give you newest first
no good for sort because sort already supports -r
no need it for tail on large files because tail already skips to the end.
I do a lot of impromptu bash to sus crap out of logs.
when you’re balls deep in
cat log|grep -v foo| rev|cut -f 1-3 -d \ | |rev
Sometimes tac comes in clutch.
That’s fair. I’d usually just use less and drop to the end. My use cases would always need the older log before a newer log though because that’s the start of the problem. At least that’s how I operate.