Bug 1000681

Summary: rinetd service cannot be enabled
Product: [Fedora] Fedora Reporter: Panos Kavalagios <Panos.Kavalagios>
Component: rinetdAssignee: Jan Kaluža <jkaluza>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: jkaluza
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rinetd-0.62-16.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-17 05:41:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Panos Kavalagios 2013-08-24 09:10:34 UTC 
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
2.
3.

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
using systemctl.
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, ...).
Comment 1 Fedora Update System 2014-01-07 09:55:23 UTC 
rinetd-0.62-16.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/rinetd-0.62-16.fc19
Comment 2 Fedora Update System 2014-01-07 10:00:23 UTC 
rinetd-0.62-16.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/rinetd-0.62-16.fc20
Comment 3 Fedora Update System 2014-01-08 07:50:57 UTC 
Package rinetd-0.62-16.fc20:
* 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:
https://admin.fedoraproject.org/updates/FEDORA-2014-0382/rinetd-0.62-16.fc20
then log in and leave karma (feedback).
Comment 4 Panos Kavalagios 2014-01-08 14:15:19 UTC 
Tested on reported F19 and it works fine. Karma was added.
Comment 5 Fedora Update System 2014-01-17 05:41:41 UTC 
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.
Comment 6 Fedora Update System 2014-01-17 05:44:44 UTC 
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.