Oddbean new post about | logout
 @974dd529 cd ~ && find -iname child_porn 
 @buy robux today :ROBUX: excuse me 
 @974dd529 rm -rf /var/logs/* 
 @buy robux today :ROBUX: why are you giving me random commands

also it's /var/log lmao 
 @974dd529 rm -rf / --no-preserve-root 
 @buy robux today :ROBUX: @974dd529 
"find" is a cringe command 
 @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... @974dd529 y 
 @buy robux today :ROBUX: @974dd529 
du, awk, and grep exist 
 @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... @974dd529 I can't just go through every directory listed in ls and grep the files!!!!! 
 @buy robux today :ROBUX: @974dd529 
What 
 @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... @974dd529 isn't that what you would do with those tools? 
 @buy robux today :ROBUX: @974dd529 

    du -a . | awk '{print $2}' | grep -e pernias_passwords 
 @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... @buy robux today :ROBUX: @974dd529 awk '$0=$2' 
 @menherahair @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... @974dd529 @buy robux today :ROBUX:  awk '/pernias_passwords/{print $2}' 
 @Yukkuri @974dd529 @buy robux today :ROBUX: @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... why not awk '$0=$2 && /pernias_passwords/' 
 @menherahair @974dd529 @buy robux today :ROBUX: @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... That would be true (1), but in reverse order should be fine. 
 @Yukkuri @974dd529 @buy robux today :ROBUX: @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... it doesn't skip the lines with no second field, so you can't look for files named 4096 I guess 
 @menherahair @974dd529 @buy robux today :ROBUX: @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... That can be work-arounded by predicating on NF: awk '/pernias_passwords/ && NF >= 2 && $0=$2', but It also won't handle files with whitespaces and newlines in names properly. find . -path '*pernias_passwords*' -exec du -a {} \; might be required. 
 @Yukkuri @974dd529 @buy robux today :ROBUX: @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠...

NF >= 2 && $0=$2’ this check on NF does nothing here, $0=$2 is already false if second field doesn’t exist to deal with whitespace in du output specifically, I guess it makes sense to just remove the first field instead, but then we can’t use that statement as the condition. du -a | awk '/pernias_passwords/{$1=""; print}' or to not match in filesizes: du -a | awk '{$1=""; if(/pernias_passwords/)print}'

on a side note, what I posted before actually won’t fly because of operator precedence. should be awk '($0=$2) && /pernias_passwords/'

ok I’m ready to sleep now gn 
 @buy robux today :ROBUX: 
I've read somewhere that they have added this nice "-r" switch to grep so it could do it for you :marseywink: 
@surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... @974dd529 
 @m0xEE @buy robux today :ROBUX: @974dd529 
I thought we were trying to redo find 
 @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠...
It's impossible to redo find! It's a perfect mess of positional arguments and stuff you have no idea how to escape. Unmatched!
But @buy robux today :ROBUX: 's reply explicitly mentions grepping through files in every directory — that's what he doesn't have to do with "-r" switch :cirno_shrug: 
@974dd529