grep processes list avoiding the grep itself
user@ubuntu:~$ ps axu | grep [a]pache2 root 9399 0.0 0.1 105628 7588 ? SNs 11:55 0:01 /usr/sbin/apache2 -k start www-data 9401 0.0 0.1 105716 5576 ? SN 11:55 0:00 /usr/sbin/apache2 -k start www-data 9402 0.0 0.1 105716 5572 ? SN 11:55 0:00 /usr/sbin/apache2 -k start www-data 9403 0.0 0.1 105668 5028 ? SN 11:55 0:00 /usr/sbin/apache2 -k start www-data 9404 0.0 0.1 105716 5576 ? SN 11:55 0:00 /usr/sbin/apache2 -k start www-data 9405 0.0 0.1 105652 4788 ? SN 11:55 0:00 /usr/sbin/apache2 -k start www-data 15581 0.0 0.1 105652 4788 ? SN 12:04 0:00 /usr/sbin/apache2 -k start www-data 15582 0.0 0.1 105652 4788 ? SN 12:04 0:00 /usr/sbin/apache2 -k start www-data 15583 0.0 0.1 105652 4788 ? SN 12:04 0:00 /usr/sbin/apache2 -k start
10 Alternatives + Submit Alt
-
As an alternative to using an additional grep -v grep you can use a simple regular expression in the search pattern (first letter is something out of the single letter list ;-)) to drop the grep command itself. Show Sample Output
72ps aux | grep [p]rocess-name -
Get the PID of a process by name Show Sample Output
11pgrep command_name -
preferred way to query ps for a specific process name (not supported with all flavors of ps, but will work on just about any linux afaik) Show Sample Output
6ps -C command -
faster ;) but your idea is really cool
6ps -ef | grep c\\ommand -
This does the same thing as many of the 'grep' based alternatives but allows a more finite control over the output. For example if you only wanted the process ID you could change the command:
ps -ef | awk '/mingetty/ && !/awk/ {print $2}'If you wanted to kill the returned PID's:ps -ef | awk '/mingetty/ && !/awk/ {print $2}' | xargs -i kill {}Show Sample Output1ps -ef | awk '/process-name/ && !/awk/ {print}'
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)
ps axu | grep apa\\chedouble backslash can be anywhere within the patternauxer () { ps aux | grep -i "$(echo "$1" | sed "s/^\(.\)\(.*$\)/\[\1\]\2/")" }pgrep -l apache2pgrep apache2