I like this method because I can make use of pgrep which also has the -f flag that can use regex to match patterns in the full command line string. It will also do ps -fww on all pids returned by pgrep, providing a list of process matching the regex provided. Show Sample Output
tested on solaris 10
On debian parent process is running as root, workers as www-data. You can run strace in backgroud, get its PID, curl your webpage, kill strace and read your stats.
Use pgrep's flexibility to search for processes, with pretty formatting via ps. All parameters are passed to pgrep. Show Sample Output
process name , process id , xms( initial memory allocation pool) , xmx(maximum memory allocation pool) Show Sample Output
Stop all docker containers
Given a process name (kdiff3 in this example) that keeps auto-spawning/starting, auto-kill until it stops, assuming there is an upper limit (if not, reboot). This was beneficial after I clicked the DIFF button in a git GUI on a merge commit. 2000+ files were being opened one after the other in my diff program (kdiff3). Each time I closed one (or quit Kdiff3), the next file would be auto-opened in Kdiff3.
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.
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
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: