Bug 147664
Summary: | 'wait=yes' parameter in /etc/xinetd.d/* files doesn't work for non-INTERNAL services | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew Zabolotny <anpaza> |
Component: | xinetd | Assignee: | Jay Fenlason <fenlason> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | jfeeney, linux_4ever |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | http://cs.ozerki.net/zap/xinetd-bug/ | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-03-22 18:48:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew Zabolotny
2005-02-10 07:06:00 UTC
I'm the upstream maintainer of Xinetd. A wait service is one that accepts the connection. telnet does not accept the connection - it expects the connection to be accepted and the socket dup'ed to the stdin/out descriptors. There is also no way for xinetd to check to see if a child has accepted the connection. Therefore, when you have a program that's configured as a wait service and it doesn't accept the connection, the socket is still readable when xinetd goes back to the select loop. Around and around it goes. This bug report can be closed - not a bug. |