Bug 76636 - xinetd-2.3.9 suddenly requires entry in /etc/services
Summary: xinetd-2.3.9 suddenly requires entry in /etc/services
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xinetd   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2002-10-24 13:15 UTC by Jan Iven
Modified: 2007-04-18 16:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-16 23:53:18 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jan Iven 2002-10-24 13:15:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
the security-fixed xinetd-2.3.9-0.72 suddenly insists that services are
to be declared in /etc/services. This defeats the nice way of adding things to
xinetd by simply dropping a file into /etc/xinetd.d/, and requires to touch a
shared file through scripts again. Yuck.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. create a new service in /etc/xinetd.d/dummy
service dummy
    port        = 6101
    socket_type = stream
    protocol    = tcp
    wait        = no
    user        = nobody
    server      = /bin/cat

2. service xinetd restart
3. telnet localhost 6101

Actual Results:  telnet says:
telnet: connect to address Connection refused

in /var/log/messages:
Oct 24 15:07:12 xxxx xinetd[31337]: service/protocol combination not in
/etc/services: dummy/tcp
Oct 24 15:07:12 xxxx xinetd[31337]: xinetd Version 2.3.9 started with libwrap
options compiled in.

Expected Results:  telnet localhost 6101
Connected to localhost.
Escape character is '^]'.

Additional info:

We really liked the fact that xinetd will take new services straight out of the
rpm, without any messing around in /etc/inetd.conf or /etc/services. And now
that we have conviced people to deploy using RPMs, all of a sudden this breaks
on installed systems. Please consider fixing ASAP.

Comment 1 Bill Nottingham 2002-12-03 20:55:47 UTC
Well, the new errata is 2.3.7-based (for other reasons), which may solve this
for you.

Comment 2 Jay Fenlason 2003-01-16 23:53:18 UTC
Newer versions of xinetd require
type            = UNLISTED
in any services that aren't listed in /etc/services.  I've just confirmed that
2.3.10 works as expected once you include that line in your dummy service

Note You need to log in before you can comment on or make changes to this bug.