[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath

2019-08-20 Thread Eric Desrochers
** Changed in: procps (Ubuntu Xenial)
 Assignee: Eric Desrochers (slashd) => (unassigned)

-- 
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/1839329

Title:
  pgrep: allows long command lines to be searched e.g. java process with
  long classpath

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  In Progress
Status in procps source package in Bionic:
  Fix Released
Status in procps source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The pgrep -f and pkill -f commands are unable to find processes strings in 
processes which are beyond the 4096th character. This often happens with Java 
command lines with long classpaths on the command line.

  [Test Case]
  A quick test to reproduce this is to vi a file using a filename over 4k
  $ vi $(seq 1 1250| paste -s -d'_')_foo.txt)
  and leave vi running then run from another terminal
  $ pgrep -af 'foo.txt'
  to find it.

  Without the fix, one will only see the first 4096 chars, while the
  expected  behaviour would be:

  $ pgrep -af 'foo.txt'
  27667 vi 

[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath

2019-08-20 Thread Launchpad Bug Tracker
This bug was fixed in the package procps - 2:3.3.12-3ubuntu1.2

---
procps (2:3.3.12-3ubuntu1.2) bionic; urgency=medium

  * d/p/pgrep-increase-CMDSTRSIZE.patch:
- Allows long command lines to be searched.
eg: Java process with a long classpath. (LP: #1839329)

 -- Eric Desrochers   Fri, 09 Aug 2019
15:37:27 +

** Changed in: procps (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
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/1839329

Title:
  pgrep: allows long command lines to be searched e.g. java process with
  long classpath

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  In Progress
Status in procps source package in Bionic:
  Fix Released
Status in procps source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The pgrep -f and pkill -f commands are unable to find processes strings in 
processes which are beyond the 4096th character. This often happens with Java 
command lines with long classpaths on the command line.

  [Test Case]
  A quick test to reproduce this is to vi a file using a filename over 4k
  $ vi $(seq 1 1250| paste -s -d'_')_foo.txt)
  and leave vi running then run from another terminal
  $ pgrep -af 'foo.txt'
  to find it.

  Without the fix, one will only see the first 4096 chars, while the
  expected  behaviour would be:

  $ pgrep -af 'foo.txt'
  27667 vi 

[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath

2019-08-20 Thread Launchpad Bug Tracker
This bug was fixed in the package procps - 2:3.3.15-2ubuntu2.1

---
procps (2:3.3.15-2ubuntu2.1) disco; urgency=medium

  * d/p/pgrep-increase-CMDSTRSIZE.patch:
- Allows long command lines to be searched.
eg: Java process with a long classpath. (LP: #1839329)

 -- Eric Desrochers   Fri, 09 Aug 2019
15:14:56 +

** Changed in: procps (Ubuntu Disco)
   Status: Fix Committed => Fix Released

-- 
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/1839329

Title:
  pgrep: allows long command lines to be searched e.g. java process with
  long classpath

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  In Progress
Status in procps source package in Bionic:
  Fix Released
Status in procps source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The pgrep -f and pkill -f commands are unable to find processes strings in 
processes which are beyond the 4096th character. This often happens with Java 
command lines with long classpaths on the command line.

  [Test Case]
  A quick test to reproduce this is to vi a file using a filename over 4k
  $ vi $(seq 1 1250| paste -s -d'_')_foo.txt)
  and leave vi running then run from another terminal
  $ pgrep -af 'foo.txt'
  to find it.

  Without the fix, one will only see the first 4096 chars, while the
  expected  behaviour would be:

  $ pgrep -af 'foo.txt'
  27667 vi 

[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath

2019-08-09 Thread Eric Desrochers
[VERIFICATION DISCO]

I have installed the disco-proposed 'procps' package and was able to
conclude that it fixes the situation based on the reproducer suggested
upstream:

$ vi $(seq 1 1250| paste -s -d'_')_foo.txt # Creating a process containing > 
4096 chars, to be precise 5158 chars)
$ pgrep -af 'foo.txt'
1148 vi 

[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath

2019-08-09 Thread Eric Desrochers
[VERIFICATION BIONIC]

I have installed the bionic-proposed 'procps' package and was able to
conclude that it fixes the situation based on the reproducer suggested
upstream:

$ vi $(seq 1 1250| paste -s -d'_')_foo.txt # Creating a process containing > 
4096 chars, to be precise 5158 chars)
$ pgrep -af 'foo.txt'
1148 vi 

[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath

2019-08-09 Thread Łukasz Zemczak
Hello Pedro, or anyone else affected,

Accepted procps into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:3.3.12-3ubuntu1.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: procps (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

-- 
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/1839329

Title:
  pgrep: allows long command lines to be searched e.g. java process with
  long classpath

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  In Progress
Status in procps source package in Bionic:
  Fix Committed
Status in procps source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  The pgrep -f and pkill -f commands are unable to find processes strings in 
processes which are beyond the 4096th character. This often happens with Java 
command lines with long classpaths on the command line.

  [Test Case]
  A quick test to reproduce this is to vi a file using a filename over 4k
  $ vi $(seq 1 1250| paste -s -d'_')_foo.txt)
  and leave vi running then run from another terminal
  $ pgrep -af 'foo.txt'
  to find it.

  Without the fix, one will only see the first 4096 chars, while the
  expected  behaviour would be:

  $ pgrep -af 'foo.txt'
  27667 vi 

[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath

2019-08-09 Thread Łukasz Zemczak
Ok, change seems to be trivial enough to accept even without getting
this merged upstream (most important is that there was no disagreement
so far from the maintainers). I also don't expect anything to go bad
since the constant bump is not too big anyway.

** Changed in: procps (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

-- 
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/1839329

Title:
  pgrep: allows long command lines to be searched e.g. java process with
  long classpath

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  In Progress
Status in procps source package in Bionic:
  Fix Committed
Status in procps source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  The pgrep -f and pkill -f commands are unable to find processes strings in 
processes which are beyond the 4096th character. This often happens with Java 
command lines with long classpaths on the command line.

  [Test Case]
  A quick test to reproduce this is to vi a file using a filename over 4k
  $ vi $(seq 1 1250| paste -s -d'_')_foo.txt)
  and leave vi running then run from another terminal
  $ pgrep -af 'foo.txt'
  to find it.

  Without the fix, one will only see the first 4096 chars, while the
  expected  behaviour would be:

  $ pgrep -af 'foo.txt'
  27667 vi 

[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath

2019-08-09 Thread Launchpad Bug Tracker
This bug was fixed in the package procps - 2:3.3.15-2ubuntu3

---
procps (2:3.3.15-2ubuntu3) eoan; urgency=medium

  * d/p/pgrep-increase-CMDSTRSIZE.patch:
- Allows long command lines to be searched.
eg: Java process with a long classpath. (LP: #1839329)

 -- Eric Desrochers   Thu, 08 Aug 2019
16:46:48 +

** Changed in: procps (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
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/1839329

Title:
  pgrep: allows long command lines to be searched e.g. java process with
  long classpath

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  In Progress
Status in procps source package in Bionic:
  In Progress
Status in procps source package in Disco:
  In Progress

Bug description:
  [Impact]
  The pgrep -f and pkill -f commands are unable to find processes strings in 
processes which are beyond the 4096th character. This often happens with Java 
command lines with long classpaths on the command line.

  [Test Case]
  A quick test to reproduce this is to vi a file using a filename over 4k
  $ vi $(seq 1 1250| paste -s -d'_')_foo.txt)
  and leave vi running then run from another terminal
  $ pgrep -af 'foo.txt'
  to find it.

  Without the fix, one will only see the first 4096 chars, while the
  expected  behaviour would be:

  $ pgrep -af 'foo.txt'
  27667 vi