The snippet below (from an existing script) is used to check the xvfb processes and whether they are listening on a specific port:  my_list=`pgrep -u $CurrentUserID -fl Xvfb | grep :${XVFBPORT}`  process_list=`pgrep -fl Xvfb | grep :${XVFBPORT}`The Xvfb process is started in the following format:  Xvfb :619  -fp /usr/share/fonts/X11/misc # i.e. in this case XVFBPORT is 619Apparently this does not work as intended on Ubuntu since the output of pgrep -fl Xvfbwould give something like:  4812 Xvfb, without the :619 at the end. Clearly, with some additional piping to ps this can be easily fixed.Is there some other distro or configuration where pgrep would give the output as expected by the script? 
Does pgrep output ever include the parameters supplied to the process?
linux;ubuntu;ps
A recent version of pgrep from procps-ng has the -a option.   -a, --list-full          List  the  full  command line as well as the process ID.So the pgrep -afl Xvfb | grep 619 should print:  4812 Xvfb :619  -fp /usr/share/fonts/X11/misOn my Debian Jessie (testing) this option is present, and the installed package is procps-ng 3.3.9, but I can't find a version when this option was introduced, perhaps the option is present in procps-ng and doesn't exist in procps.