Red Hat Bugzilla – Bug 746084
matahari services missing from chkconfig
Last modified: 2011-12-06 06:45:27 EST
Description of problem:
Summary says it all, after installing matahari on a fresh os I noticed that none of the services are in the chkconfig --list output. They can be manually added by running 'chkconfig --add service-name'.
Also, not sure if this is an additional issue but when chasing this bug, I looked at the init script and noticed that the Provides value is not filled in for any of the matahari services.
### BEGIN INIT INFO
# Required-Start: $local_fs matahari-broker
Compared to libvirt-qmf which does have a value.
### BEGIN INIT INFO
# Provides: libvirt-qmf
# Should-Start: libvirtd
This is the case on all arches
Version-Release number of selected component (if applicable):
Thinking about how to implement some test automation intelligence to run test variants depending on their arch I came across this web page which is making me question if matahari services for Fedora are properly configured for startup on next boot.
[root@localhost ~]# ls /etc/systemd/system/*.wants/matahari*
ls: cannot access /etc/systemd/system/*.wants/matahari*: No such file or directory
[root@localhost ~]# ls /etc/systemd/system/*.wants
email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org
crond.service remote-fs.target rsyslog.service
Fix committed to spec file in upstream repo:
good to go in v0.4.4-9
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
No description required.
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.