A Unix Utility to Know About: lsof (2009)

Post by LukeShu » Sat, Aug 27, 2016, 2:57 AM UTC

_c_ wrote: post #50

LukeShu wrote: post #42

Earlier quoted context omitted.

You don't need any of those `exec`s. Yes, GNU grep has `-a`. If you don't like the backslash-newline-pipe sequence, if you put the pipe at the end of the previous line, you don't need the backslash; but it's less obvious that the next line is operating on the output of the previous. Multi-line arguments to sed can be a pain (good luck getting your editor to auto-indent them). Instead, you can use -e to specify multip…

Thanks for taking the time to comment. Multiple arguments could be added if you want that. I personally do not need it as I search the cmdline patterns I need without using spaces. I use dots instead. Quick and dirty. I write 100's of these small scripts for my own use only so I have my own style, peculiar as it may be. I never need indentation because I always keep scripts short; I only use it occasionally and rando…

Post by smhenderson » Mon, Aug 29, 2016, 4:11 PM UTC

amyjess wrote: post #46

smhenderson wrote: post #41

Earlier quoted context omitted.

Yeah, I always felt having to type the extra bit was strange, like maybe grep could have a switch to say "don't find grep" but I guess having a switch for such a specific use case, grepping processes, is overkill. Anyway, it's just a reflex now to always: ps aux | grep | grep -v grep

You can also surround each character in the program's name with square brackets. ps -ef | grep [p][r][o][g][r][a][m]