Red Hat Bugzilla – Bug 78903
xinetd redirect does not work after update
Last modified: 2014-08-31 19:24:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021128
Description of problem:
xinetd redirect does not work after latest errata update:
disable = no
user = nobody
socket_type = stream
wait = no
redirect = 184.108.40.206 110
This service does not work after latest errata update (xinetd-2.3.7-4.7x)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I am also seeing this problem.
Yep it's true, xinetd-2.3.7-4.7x completely ignores services with redirect
statements! They don't even appear in debug output (running xinetd -d).
The redirect facility in xinetd is full of problems. There have been and there
still are problems with xinetd being unable to reload config properly and
being unable to re-enable services after they are temp. disabled and so on.
It's a whole mess. Please see bugs #60049 and #76727.
I tried 2.3.7-5 from RHL 8.0 errata (rebuilt it for 7.3 from SRPMS), no luck.
Still the same.
Then I tried a build using the plain 2.3.9 sources. I really have no clue as
to what evil things this version can do, but at least redirect works with it,
or so it seems for the time being.
*** Bug 83204 has been marked as a duplicate of this bug. ***
This is basic functionality for xinetd. You've issued two updates to xinetd on
7.3 and they've both been broken. How about fixing this?
I also verified this bug, redirect does not work.
I tried the same configuration on a redhat 9 box and the redirect works well.
What about a fix, I find this bug really annoying.
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.