Red Hat Bugzilla – Bug 1000681
rinetd service cannot be enabled
Last modified: 2014-01-17 00:44:44 EST
Description of problem: rinetd service cannot be enabled.
Version-Release number of selected component (if applicable): rinetd-0.62-14.fc19.x86_64
How reproducible: Enable the service
Steps to Reproduce:
1. Run: systemctl enable rinetd.service
Actual results: The service cannot be started.
Expected results: The service should have been installed.
Additional info: The following output is printed:
# systemctl enable rinetd.service
The unit files have no [Install] section. They are not meant to be enabled
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
rinetd-0.62-16.fc19 has been submitted as an update for Fedora 19.
rinetd-0.62-16.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rinetd-0.62-16.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Tested on reported F19 and it works fine. Karma was added.
rinetd-0.62-16.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
rinetd-0.62-16.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.