How to prevent "ps" reporting its own process?

Question

$ ps | grep django
28006 ttys004    0:01.12 /usr/bin/python bin/django celeryd --beat
51393 ttys005    0:01.45 /usr/bin/python bin/django celeryd -l INFO
51472 ttys005    0:01.29 /usr/bin/python bin/django celeryd -l INFO
51510 ttys005    0:01.89 /usr/bin/python bin/django celeryd -l INFO
51801 ttys005    0:01.83 /usr/bin/python bin/django celeryd -l INFO
53470 ttys005    0:03.97 /usr/bin/python bin/django celeryd -l INFO
53780 ttys005    0:00.00 grep django

Is there a way to prevent the last process (that is, the grep that was started at the same time as my ps command) being reported?

(I started trying to come up with a regex that would match the literal but not match itself, but that seemed, um, not the right approach...)

score 68 · Answer 1 · answered Mar 09 '12 at 07:54

68

+1 for @jamzed terse answer, however the OP might need some explanation:

ps | grep "[d]jango"

Using that regex you are launching a process which its ps string will not match itself, since the regexp matches "django" and not "[d]jango". That way you'll exclude the process that has the string "[d]jango" which in this case is grep; The same can be applied to pgrep, egrep, awk, sed, etc... whichever command you used to define the regex.

From man 7 regex

   A bracket expression is a list of characters enclosed in "[]".  It nor‐
   mally matches any single character from the list (but see  below).   If
   the  list  begins  with  '^',  it matches any single character (but see
   below) not from the rest of the list.  If two characters  in  the  list
   are  separated  by '-', this is shorthand for the full range of charac‐
   ters between those two (inclusive) in the collating sequence, for exam‐
   ple,  "[0-9]" in ASCII matches any decimal digit.  It is illegal(!) for
   two ranges to share an endpoint, for example, "a-c-e".  Ranges are very
   collating-sequence-dependent,  and portable programs should avoid rely‐
   ing on them.

answered Mar 09 '12 at 07:54

hmontoliu

3,693
3
22
24

2

Cool. I'm actually pretty comfortable with regexs but couldn't immediately think of a way to prevent the regexp matching itself. Enclosing a letter in square brackets makes perfect sense. (Including something like [^!] would also work...) – Steve Bennett Mar 09 '12 at 11:23
1

That's nice and crafty. – ash Mar 09 '12 at 21:09
For the 'ps' specific case, I use '[ ]' at the front of the process name I am searching for. Then I don't need to parse the process name specially for the regex, but it still matches. – Neromancer Nov 05 '14 at 11:05
@hmontoliu It does not work for example: `ps aux | grep [s]cript1`. Could you help to comment about the solution ? – SOUser Nov 13 '17 at 14:05
@hmontoliu My fault. It seems the line is shown because of the previous searches... – SOUser Nov 13 '17 at 14:09

score 31 · Answer 2 · edited Mar 09 '12 at 13:31

31

ps | grep [d]jango

ps | grep d[j]ango

...

ps | grep djang[o]

edited Mar 09 '12 at 13:31

Ilmari Karonen

895
5
11

answered Mar 09 '12 at 07:10

jamzed

1,080
7
8

Add space if you need to grep one char: `ps aux| grep "[Z] "` – A.D. Jun 05 '15 at 12:12
@jamzed It does not work for example: `ps aux | grep [s]cript1` or `ps aux | grep [s]cript2`. The grep line is still shown. Could you help to comment about the solution ? – SOUser Nov 13 '17 at 14:05
@jamzed My fault. It seems the line is shown because of the previous searches... – SOUser Nov 13 '17 at 14:09

score 19 · Answer 3 · edited Nov 29 '12 at 06:28

19

Use pgrep instead: pgrep -lf django

edited Nov 29 '12 at 06:28

quanta

50,327
19
152
213

answered Mar 09 '12 at 06:19

ramruma

2,730
1
14
8

As usual I forgot to mention the platform (OS X in this case). Presumably pgrep works on various linuxes. – Steve Bennett Mar 09 '12 at 11:30
I don't agree, @ramruma . I came to this thread precisely because `pgrep`gives me exactly this problem. But I must say I am testing it in CygWin (where `ps` can not show the full command line of the process). – Sopalajo de Arrierez Apr 04 '14 at 02:28
The manual states "The running pgrep or pkill process will never report itself as a match.", and indeed I've not seen it do so. – deltab Mar 07 '16 at 02:07
I've just been dealing with a problem where I thought `pgrep` was matching itself. Turns out it was matching the name of the `bash` script file I was running it from. Adding `-x` fixed it, then it does an exact match on the command name. – andynormancx Mar 14 '19 at 10:43

score 19 · Accepted Answer · edited Mar 06 '16 at 23:57

My answer is a variation on the typical answer for searching for "foobar" in a ps listing. The argument of "-A" "ps" is more portable than "aux", I believe, but this change is irrelevant to the answer. The typical answer looks like this:

$ ps -A -ww | grep [f]oobar

Instead I use this pattern:

$ ps -A -ww | grep [^]]foobar

The main advantage is that it's easier to write scripts based on this patterns because you simply concatenate a static string [^]] with whatever pattern you are looking for. You don't need to strip off the first letter of the string then insert it between the square braces and then concatenate the that back together again. When scripting in shell it's easier to simply stick [^]] in front of the pattern you were lookginfor looking for. String slicing in Bash is an ugly thing, so my variation avoids that. This variation says show the lines where the pattern matches WITHOUT a leading right-square-bracket ]. Since the search pattern to exclude a square bracket actually adds the square bracket to the pattern then it will never match itself.

So you could write a portable psgrep command as follows. Here, I make some allowance for differences between Linux, OS X BSD, and others. This adds the column headers from ps, provides a more custom ps format that suits my needs betters, and displays processes listing extra, extra wide so that none of the command-line arguments are missed. Well, most are not missed. Java being Java, it often does things in the worst possible way, so you some java services will run past the maximum allowed length of arguments that the process table will keep track of. I believe this is 1024 characters. The command-lone length allowed to start a process is much longer, but the kernel process table doesn't bother to keep track of anything over 1K in length. Once the command is started the command-name and argument list isn't needed against, so what gets stored in the process table is just informational.

psgrep ()
{
    pattern=[^]]${1};
    case "$(uname -s)" in
        Darwin)
            ps -A -ww -o pid,ppid,nice,pri,pcpu,pmem,etime,user,wchan,stat,command | grep -i -e "^[[:space:]]*PID" -e ${pattern}
        ;;
        Linux)
            ps -A -ww -o pid,ppid,tid,nice,pri,pcpu,pmem,etime,user,wchan:20,stat,command | grep -i -e "^[[:space:]]*PID" -e ${pattern}
        ;;
        *)  # other UNIX flavors get a minimalist version.
            ps -A -ww | grep -i -e ${pattern}
        ;;
    esac
}

Disadvantage is that this will actually match one char more (in front) than the original pattern. For exemple, this will never match the PID. And can be a bit misleading when used with `grep --colour`. — Læti, Sep 19 '18 at 19:31

score 11 · Answer 5 · answered Mar 09 '12 at 05:46

11

Oh wait, this works:

ps | grep django | grep -v grep

answered Mar 09 '12 at 05:46

Steve Bennett

5,539
12
45
57

7

Only if the process command line doesn't legitimately include `grep`, which you cannot count on in the general case. – user Mar 09 '12 at 12:41

score 8 · Answer 6 · edited Jan 04 '13 at 07:28

8

ps -d | grep django

from man ps:

 -d                  Lists information  about  all  processes
                     except session leaders.

edited Jan 04 '13 at 07:28

quanta

50,327
19
152
213

answered Oct 23 '12 at 14:08

blah

81
1
1

still shows grep on mine... – Kevin Jun 23 '13 at 21:03
Yep, that works for me on OS X. – Steve Bennett Jan 29 '14 at 05:54
Doesn't work so well on Linux. – Asclepius Aug 18 '14 at 21:55
More generally, the options to `ps` are notoriously non-portable, so without information about which platform this is for, this answer isn't very helpful. Furthermore, this is obviously not adequate when you are not sure that the process you are looking for is not a process leader (i.e. this may help if your target is a daemon, but not generally otherwise). – tripleee Apr 05 '16 at 11:51
Funny, on Mac this seems to *only* show the grep process and filters everything else out. – Christopher Hunter Nov 09 '18 at 22:50

pt1997 · Answer 7 · 2021-08-12T06:53:55.860

2

This only occurs to me when running inside an ssh "script" command or when using remote management tools. I don't like the hackiness of the previous solutions. I'm not sure if what I've come up with is better but here you go:

| grep -v $$

$$ is replaced by the PID of the ps/pgrep "process" and -v tells grep to not print it.

demo:

watch date &
bash -c 'echo; pgrep -lfa watch | grep -v $$'

the bash -c and the echo are only needed to simulate the mentioned situation and because otherwise pgrep would not report itself.

edited Aug 12 '21 at 06:53

answered Aug 11 '21 at 13:33

pt1997

21
2

What is `watch` meant to do in this context? – Steve Bennett Aug 11 '21 at 23:19
it is just used as a demo process, running in the background, to search for. – pt1997 Aug 12 '21 at 06:48

How to prevent "ps" reporting its own process?

7 Answers7

Linked