Pgrep in procd init script Generates Phantom? PID

For Developers
1

I use a call to pgrep <process name> -> stdout in a procd init script. It's worked admirably for months until recently. Now it seems to generate an additional unknown Phantom PID.

The init script function says simply send pgrep <process name> to stdout, but now I see what to all intents seems to be a Phantom process added.

Call pgrep <process name> from init script generates this to stdout

   PID(s)
===========
3367--\
3368   |-->valid output
3369--/
**22740** *Phantom Process ?*

If I issue pgrep <process name> from CLI it returns the expected result as:

3367	
3368	
3369

and if I call ps from CLI, I never see the Phantom process listed:

PID USER
22497 root      1220 S    ash ./testps
22519 root      1228 R    ps
31387 root      7560 SN   /usr/sbin/collectd -C /tmp/collectd.conf -f

Has something changed with BusyBox in recent Snapshot?

2

Maybe the init script name matches the name of the process you're grepping for

3

This is true, but it doesn't explain why the Phantom PID has only shown up recently when the script hasn't been updated since March 2021. It always just displayed the PID of each config_foreach start_instance

The other odd thing about it is that the Phantom PID that is displayed now is always +20 more than the PID of the previous itteration.

   PID(s)
===========
25677=====\
25678      |=====> these are the PIDs of each config_foreach start_instance
25679=====/
27004  Phantom PID
       Note the Phantom PID progression if I invoke multiple itterations of the script function
27024
27044
27064
27084
27104
27124
27144
27164
27184