This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1327226 - pmie not responding to signals
pmie not responding to signals
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: pcp (Show other bugs)
23
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Nathan Scott
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-14 10:06 EDT by Marko Myllynen
Modified: 2016-09-05 22:20 EDT (History)
8 users (show)

See Also:
Fixed In Version: pcp-3.11.4-1.el5 pcp-3.11.4-1.fc24 pcp-3.11.4-1.fc23
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-09-05 15:49:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marko Myllynen 2016-04-14 10:06:13 EDT
Description of problem:
After doing

$ pmie

you need to send a SIGKILL to terminate it.
Comment 1 Marko Myllynen 2016-07-21 14:11:28 EDT
Seems that SIGQUIT also does the job; SIGTERM/SIGHUP/SIGINT doesn't. So perhaps it's a feature?
Comment 2 Ken McDonell 2016-07-21 16:43:25 EDT
This is NOT a bug.

From the pmie(1) man page ...

       The expressions to be evaluated are read from configuration files spec‐
       ified by one or more filename arguments.  In the absence of  any  file‐
       name, expressions are read from standard input.

Please close this bug.
Comment 3 Frank Ch. Eigler 2016-07-21 16:52:44 EDT
Most UNIX tools that parse their standard input also respect SIGINT etc. as a termination signal.  If pmie feels it must block those during input parsing, this unusual behaviour should be documented.
Comment 4 Ken McDonell 2016-07-21 17:31:40 EDT
You are correct Farnk, my apologies.

I have committed the necessary (almost) trivial fix.
Comment 5 Fedora Update System 2016-08-15 21:55:26 EDT
pcp-3.11.4-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b76275250f
Comment 6 Fedora Update System 2016-08-16 01:16:27 EDT
pcp-3.11.4-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-a51156083f
Comment 7 Fedora Update System 2016-08-16 01:56:40 EDT
pcp-3.11.4-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-415f0c78ed
Comment 8 Fedora Update System 2016-09-05 15:48:43 EDT
pcp-3.11.4-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2016-09-05 18:53:18 EDT
pcp-3.11.4-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
Comment 10 Fedora Update System 2016-09-05 22:19:45 EDT
pcp-3.11.4-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.