RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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.

Instance usage example.

systemctl enable xinetd-inbuilt

I don't understand why you would want to do something like this. Why not call chkconfig directly?

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.