Red Hat Bugzilla – Bug 56484
xinetd.d/tftp config invalid, results in errors, non-functioning service.
Last modified: 2007-04-18 12:38:21 EDT
Description of Problem:
The /etc/xinetd.d/tftp file tries to use two conflicting protections. The
first is to run as 'nobody' while the second is to use the -s parameter to
chroot() to the specified directory.
It appears, however, that the user 'nobody' is not permitted to chroot()
and so the tftp fails, logging:
tftpd: chroot: Operation not permitted
repeated many times, then:
xinetd: tftp service was deactivated because of looping
into syslog, and giving the client tftp program no feedback whatsoever
(looks like a non-responsive host).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. put a file in the tftp directory specified in the args line of
the /etc/xinetd.d/tftp file.
2. tftp localhost
3. get <filename from step one, without path>
hangs, spews errors.
changing the 'user = nobody' to 'user = root' solves the problem, and
makes the config match the pre-xinetd config in inetd.conf in older
versions of RedHat.
The user=root thing appears to exist in RHL 7.2
Please consider putting out errata for this type of thing, rather than telling
people to upgrade to the current release. Many folks are using 7.0 and can't
upgrade due to hardware issues. The errata can just be text indicating how
people can fix this manually, as opposed to putting out a fixed RPM.
This is what it's all about supporting customers on the releases they use in
production, vs. playing microsoft and telling people to just upgrade to the
That's my rant on marking bugs fixed as "CURRENTRELEASE". Now back to your
regularly scheduled programming...