Bug 38669
Summary: | /etc/xinetd.d/*-udp files syntax error on | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Dan Anderson <redhatbugzilla> |
Component: | xinetd | Assignee: | Trond Eivind Glomsrxd <teg> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-05-19 22:46:37 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
Dan Anderson
2001-05-01 23:54:27 UTC
Removing the "-udp" suffix confuses other services. Let me clarify. Both udp and tcp services can and do have the same name. Lets take "echo" as an example: $ grep echo /etc/services echo 7/tcp echo 7/udp Although /etc/xinetd.d/echo and /etc/xinetd.d/echo-udp are different file names both MUST have "echo" on the "service" line (because there's no such service called "echo-udp" # ls -l /etc/xinetd.d/echo* -rw-r--r-- 1 root root 288 May 3 13:01 echo -rw-r--r-- 1 root root 343 May 3 13:00 echo-udp # cat /etc/xinetd.d/echo # default: off # description: An echo server. This is the tcp \ # version. service echo { type = INTERNAL id = echo-stream socket_type = stream protocol = tcp user = root wait = no disable = no } # cat /etc/xinetd.d/echo-udp # default: off # description: An echo server. This is the udp \ # version. # Removed -udp (bugzilla bug 38669) service echo { type = INTERNAL UNLISTED id = echo-dgram socket_type = dgram protocol = udp user = root wait = yes disable = no port = 7 } # netstat -a |grep echo tcp 0 0 *:echo *:* LISTEN udp 0 0 *:echo *:* I know that - the problems is handling it in ntsysv and chkconfig, which needs unique names for services: Note that I specify the port in an attempt at making xinetd run it with a different name. OK. Thanks for the comment. Let me just add that it sounds like ntsysv and chkconfig need to be fixed. Service names could be the same for both TCP and UDP and that this has long been standardized before ntsysv or chkconfig have existed. A fix is in xinetd-2.1.8.9pre15-1. |