Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It only takes a minute to sign up.
Sign up to join this community
# ps -ef | grep gre
root 15067 63614 0 11:03 pts/0 00:00:00 grep --color=auto gre
Another example
# ps -ef | grep sshd
root 1186 1 0 Jul26 ? 00:00:00 /usr/sbin/sshd -D
root 15439 63614 0 11:05 pts/0 00:00:00 grep --color=auto sshd
How can I stop the grep command being found by itself and not returned as a field?
The better way is to use pgrep for that task. It seems to be available on most systems these days.
There are a number of ways, more or less hacky and awkward. My favourite is to insert a double-backslash before a letter in my search string:
ps -ef | grep ss\\hd
The \\ is interpreted to \ by the shell, and \h is interpreted as equivalent to 'h' by grep. So it is effectively searching for 'sshd' as before. However, its own command string no longer contains 'sshd', it contains 'ss\hd', so it doesn't match itself.
Change the pattern so it is a regular expression that will not match the literal text.
ps -ef | grep [s]shd
When available, just use pgrep which was designed to properly overcome this issue, eg:
ps -f $(pgrep sshd)
This method is cleaner than the hackish workarounds usually suggested.
What you need is ps -e | grep sshd
(ps -ef is listing processes and their arguments, ps -e lists only the processes).
ps -fCsshd
That's probably all you need on a linux system.
You can use grep itself to avoid that result:
ps -ef|grep your_search_chain|grep -v grep
In the same way as Andrew, you can use [] :
ps -ef |grep [s]shd
It will be taken as a simple BRE regex, and will not match itself. I consider it less intrusive than the backslashes, for which you'll have to care about "what interpreter will take them into account first".
