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.

Description of problem:
Any service defined in /etc/xinetd.d/ that has an executable on an NFS mounted filesystem will not start up because systemd may not have completed mounting NFS filesystems at the time xinetd starts

How reproducible:
Consistently



Steps to Reproduce:
Create an entry in xinetd.d  (for example "nntp"port used here)
service nntp
{
        disable = no
        socket_type     = stream
        wait            = no
        user            = news
        flags           = IPv6
        server          = /nfs_mount/bin/executable
}

Reboot


Actual results:
Error in /var/log/messages saying that the executable isn't present and so the service is disabled

Expected results:
xinetd should wait for NFS so the executable is available

Additional info:
Fix is simple; add remote-fs.target to /usr/lib/systemd/system/xinetd.service

What if you wanted to run the NFS server from xinetd? Then, it wouldn't work. You should really prefer to turn your xinetd service into a systemd service. Especially if you need dependencies.