RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
  According to [1] there should be exit code 1 when tuned is killed but pid file exists.

  [1] http://fedoraproject.org/wiki/Packaging:SysVInitScript#LSB_Header

Version-Release number of selected component (if applicable):
  tuned-2.2.2-1.el7.noarch

How reproducible:


Steps to Reproduce:
  1. systemctl start tuned
  2. kill -9 `cat /var/run/tuned/tuned.pid`
  3. systemctl status tuned
  4. echo $?

Actual results:
  Exit code is 3.

Expected results:
  Exit code should be 1.

Additional info:

I think this is out of our control. It is managed by systemd, reassigning to systemd.

commit 83712936d986f2fdf7bcd2b3ea7f01ec08103cd6

(In reply to Harald Hoyer from comment #3)
> commit 83712936d986f2fdf7bcd2b3ea7f01ec08103cd6

I can't find this commit ID. Did you rebase it before pushing to upstream? I guess you meant this one:

  commit 175728c45fae8a2e1aa9d725ee2fbc7aa34e6dbf
  Author: Harald Hoyer <harald>
  Date:   Tue Jun 25 13:06:51 2013 +0200

      systemctl: conform to LSB with the "status" return code

Looking at the code, it's not clear to me how it can work. Are you sure the "PIDFile" property tells us anything about the existence of the file? Doesn't it merely mean that the unit has the "PIDFile=" directive in its unit file?

commit 3b05b8b3b503caf525fa72440a3f9f4bae75268b

better?

OK, that should work.

systemd-206-4.el7