touch-packages team mailing list archive

[Jens Elkner <jel+ubuntu@xxxxxxxxxx>]

Public bug reported:

'pgrep upstart-udev-bridge' should definitely spit out a pid, but it
doesn't. When one uses the option -f than it actually prints the PID of
the upstart-udev-bridge process. However using -f is a bad workaround,
because than (at least wrt. the man page) the arguments and operands get
included into the match, which may break scripts or even lead to
security issues.

I guess, the bug is, that p{grep|kill} strips off everything after the
first '-' of the command before it actually tries to compare with the
given operand (or something like that).

** Affects: procps (Ubuntu)
     Importance: Undecided
         Status: New

** Package changed: system-config-kickstart (Ubuntu) => procps (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1413699

Title:
  pkill|pgrep are buggy

Status in procps package in Ubuntu:
  New

Bug description:
  'pgrep upstart-udev-bridge' should definitely spit out a pid, but it
  doesn't. When one uses the option -f than it actually prints the PID
  of the upstart-udev-bridge process. However using -f is a bad
  workaround, because than (at least wrt. the man page) the arguments
  and operands get included into the match, which may break scripts or
  even lead to security issues.

  I guess, the bug is, that p{grep|kill} strips off everything after the
  first '-' of the command before it actually tries to compare with the
  given operand (or something like that).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1413699/+subscriptions