Bug 1414695

Summary: Provide native systemd unit files for all xinted inbuilt services
Product: Red Hat Enterprise Linux 7 Reporter: Jijesh Kalliyat <jkalliya>
Component: xinetdAssignee: Jan Synacek <jsynacek>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: jkalliya, mpoole, systemd-maint-list
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-25 11:50:00 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:
Embargoed:
Attachments:
Description Flags
Control script
none
xinetd service instance script none

Comment 3 Martin Poole 2017-01-19 09:54:39 UTC
Created attachment 1242424 [details]
Control script

This script "/usr/sbin/xinetd-alloff" should be used in the current xinetd systemd unit file as  ExecStartPre  to disable all services (in case ones have been manual selected outside systemd control.

Individual service control comes with an instance service script.

Comment 4 Martin Poole 2017-01-19 09:57:20 UTC
Created attachment 1242425 [details]
xinetd service instance script

This script "/usr/lib/systemd/system/xinetd-inbuilt@.service" provides the instance template for the inbuilt services of xinetd.

In fact it can be used for any xinetd controlled service.

Comment 5 Martin Poole 2017-01-19 10:00:23 UTC
Instance usage example.

systemctl enable xinetd-inbuilt

Comment 6 Jan Synacek 2017-01-19 10:44:47 UTC
I don't understand why you would want to do something like this. Why not call chkconfig directly?

Comment 7 Martin Poole 2017-01-19 11:04:57 UTC
The main point of the customer is that having to use chkconfig means they have to maintain both systemd unit files and chkconfig control scripts.

Given systemd has effectively obsoleted the need to use xinetd for anything other than its inbuilt services it makes a for a more unified experience to have xinetd provide the integration elements, via a unit template, to allow control of its internal services by using native systemctl commands.