peak amount of memory occupied by any process with "FOO" in its name
user@host:~$ grep VmHWM /proc/$(pgrep -d '/status /proc/' bash)/status /proc/1614/status:VmHWM: 9040 kB /proc/4536/status:VmHWM: 8940 kB /proc/6521/status:VmHWM: 8868 kB /proc/11742/status:VmHWM: 8760 kB /proc/14246/status:VmHWM: 8624 kB
What do you think?
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
What's this?
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Similar Commands
Stay in the loop…
- Follow the Tweets.
-
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10 - Subscribe to the feeds.
-
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
grep VmHWM $(pgrep FOO | sed 's!.*!/proc/\0/status!')A bit simpler to follow, but if the command doesn't exist, grep just sits there waiting. What we needed was xargs:pgrep FOO | xargs -rI{} grep -H VmHWM /proc/{}/statusxargs -r -- don't run if there are no matches -I{} -- capital i, replace this string {} with the matches grep -H -- force the display of the filename