Bug 1251711

Summary:	xinetd systemd service should depend on remote-fs.target
Product:	Red Hat Enterprise Linux 7	Reporter:	Stephen Harris <lists>
Component:	xinetd	Assignee:	Jan Synacek <jsynacek>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 08:13:58 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:

Description Stephen Harris 2015-08-09 02:37:46 UTC

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

Comment 2 Jan Synacek 2015-08-12 08:13:58 UTC

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.