Project

General

Profile

Bug #5839

Test suite: pgrep detects itself in remote shell

Added by Tails about 6 years ago. Updated about 5 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Test suite
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
No
Affected tool:

Description

When running 'vm.execute("pgrep -f $something")' it's currently the case that @pgrep lists its own pid (and hence never fails, which could be of great importance), unlike when you run it natively, and unlike "The running pgrep or pkill process will never report itself as a match." in pgrep(1).

The practical problem is the (potentially serious) surprise one can be hit by when writing a step definition.

Why is that happening? Are other tools misbehaving?

Having a look in the pgrep sources may help us understand this issue.

History

#1 Updated by BitingBird over 5 years ago

  • Subject changed from test suite: pgrep detects itself in remote shell to Test suite: pgrep detects itself in remote shell
  • Description updated (diff)
  • Category set to Test suite
  • Starter set to No

#2 Updated by intrigeri about 5 years ago

  • Tracker changed from Feature to Bug
  • Description updated (diff)

Also available in: Atom PDF