Looking at the man page for pgrep this isn't a bug. Looks like it is the
default behaviour for backwards compatibility with the original Solaris
version.
NOTES
The process name used for matching is limited to the 15 characters
present in the output of
/proc/pid/stat. Use the -f opt
You too noticed ps -e truncates process names.
At first, I suspected pgrep was a script over "ps -e"
but pgrep is a C executable.
ps and pgrep are both linked to libproc.so:
objdump -x /bin/ps | grep libproc
objdump -x /usr/bin/pgrep | grep libproc
NEEDED libproc-3.2.7.so
Probably/maybe a c
You too noticed ps -e truncates process names.
At first, I suspected pgrep was a script over "ps -e"
but pgrep is a C executable.
ps and pgrep are both linked to libproc.so:
objdump -x /bin/ps | grep libproc
objdump -x /usr/bin/pgrep | grep libproc
NEEDED libproc-3.2.7.so
Probably/maybe a c
** Changed in: procps (Ubuntu)
Status: Unconfirmed => Confirmed
--
pgrep cannot match some long filenames
https://bugs.launchpad.net/bugs/113096
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
I can replicate this.
It seems to be only seeing the first 15 characters of the script name.
pgrep myscriptwithalo
[shows PID]
pgrep myscriptwithalon
[shows nothing]
Is it using the output from ps -e? This seems to truncate the commands
after 15 characters.
--
pgrep cannot match some long fil
