Description of problem:
The rhel-dmesg.service does not appear to be properly setup as a
systemd service. As you can see from the below output, it is marked
as disabled, and vendor preset: disable, yet the service has quite
clearly still run.
# systemctl status rhel-dmesg
● rhel-dmesg.service - Dump dmesg to /var/log/dmesg
Loaded: loaded (/usr/lib/systemd/system/rhel-dmesg.service; disabled; vendor preset: disabled)
Active: active (exited) since Wed 2016-10-26 10:38:06 BST; 2 weeks 6 days ago
Main PID: 785 (code=exited, status=0/SUCCESS)
The rhel-dmesg.service should be properly setup within systemd such that
it is actually enabled when it is desired to be run, and can be disabled
if that behaviour is desired.
Version-Release number of selected component (if applicable):
initscripts-9.49.30-1.el7_2.3.x86_64 (also RHEL-7.3)
Steps to Reproduce:
1. Boot System
2. Run `systemctl status rhel-dmesg`
Observe that despite being disabled, the service has run
Service should be enabled if it's expected to run, and not
run if it is disabled.
=== In Red Hat Customer Portal Case 01728677 ===
--- Comment by Auchterlonie, Stuart on 15/11/2016 21:44 ---
Customer noted the following:
If I delete the symlink I mentioned it doesn't run at startup:
/usr/lib/systemd/system/basic.target.wants/rhel-dmesg.service -> ../rhel-dmesg.service
It seems there are various services that are "hard coded" by these symlinks in /usr/lib/systemd/system/*.target.wants/ that run on startup without them being enabled by an equivalent symlink in /etc/systemd/system/*.target.wants/ ... which functionally makes sense as that's the same model as unit files, but doesn't make much sense to me in terms of systemctl reporting the services as disabled even when they are effectively enabled?
Making this BZ report public, so people outside Red Hat can see it as well.
*** Bug 1478335 has been marked as a duplicate of this bug. ***
Pull-request submitted for review:
Before merging these changes, the blocking BZ #1493545 needs to be resolved.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.