Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 18915 - chkconfig doesn't read /etc/xinetd.conf
chkconfig doesn't read /etc/xinetd.conf
Product: Fedora
Classification: Fedora
Component: chkconfig (Show other bugs)
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Lukáš Nykrýn
Kevin Baker
: FutureFeature, Reopened
Depends On:
  Show dependency treegraph
Reported: 2000-10-11 15:50 EDT by Jonny Robertson
Modified: 2014-12-01 18:08 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-20 12:53:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonny Robertson 2000-10-11 15:50:57 EDT
if you have disabled services is xinetd.conf (with a disabled line),
the services have definately been disabled. (checked this with a netstat).
but when you run a chkconfig --list from the command line, it lists 
services as
being disabled _only_ if a 'disable' line is actually inside 
the /etc/xinetd.d/xxxxxx individual file itself.

or maybe this is a problem with xinetd in that you can turn the services 
off in multiple places?

new zealand
Comment 1 chrismcc 2000-10-15 23:15:50 EDT
I thought I would tack this on here as apposed to opening another bug report...
This seems to be cosmetic only.

[chrismcc@wednesday chrismcc]$ chkconfig --list
xinetd based services:
	amandaidx:	off
	amidxtape:	off
	finger:	off
	linuxconf-web:	off
	ntalk:	off
	talk:	off
	telnet:	off
	tftp:	off
	wu-ftpd:	on
	cvs:	off
	amandaidx.rpmnew:	off
	amidxtape.rpmnew:	off
	swat:	off
	imap:	on
	imaps:	on
	ipop2:	off
	ipop3:	on
	pop3s:	on

service.rpmnew gets listed and can even be manipulated
I checked, and xinetd will ignore config files ending in:
so there is no risk of accidently running these services
Comment 2 Bill Nottingham 2000-10-16 12:48:01 EDT
Correct; chkconfig doesn't read xinetd.conf at all.
Comment 3 Bill Nottingham 2000-10-19 02:44:16 EDT
.rpmnew ignoring will be added in chkconfig-1.2.17-1.
Comment 4 Henri Schlereth 2001-01-17 14:06:06 EST
Apparently fixed as of chkconfig-1.2.17-1 (RAWHIDE). If this is not the case please re-open this ticket.
Comment 5 Henri Schlereth 2001-01-17 14:07:19 EST
Sorry, should have added that I manually enabled telnet/restarted xinetd and ran checkconfig to verify that it sees it as being on.
Comment 6 Jonny Robertson 2001-01-17 18:54:13 EST
just tried upgrading to chkconfig-1.2.17-1 (RAWHIDE), and checked for the
bug i initially reported....

Still seems to be there. :((

If you tell a service in /etc/xinetd.d/ (e.g. telnet) 'disable = no', but
then say 'disable = telnet' in /etc/xinetd.conf:
it still says 'telnet: on' when you do a chkconfig --list.
But telnet _hasn't_ been started because xinetd looks at the xinetd.conf
file as well as the /etc/xinetd.d/* files and realises it needs to be

So chkconfig isn't checking this properly.

Comment 7 Daniel Roesen 2005-06-04 18:13:44 EDT
Jonny, is this still an issue in today's chkconfig?
If not, Bill: will chkconfig be enhanced to read xinetd.conf too?
Comment 8 Bill Nottingham 2005-06-06 01:44:18 EDT
I can answer the first one: the code hasn't changed.

It may be enhanced at some point in the future; barring patches appearing
elsewhere, it probably won't be too soon.
Comment 9 Red Hat Bugzilla 2007-02-05 14:31:40 EST
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
Comment 11 Fedora Admin XMLRPC Client 2012-10-18 16:01:33 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 12 Lukáš Nykrýn 2013-02-20 12:53:01 EST
Disabled in xinetd.conf should be used only as manual and temporary, so I don't think that chkconfig should parse and edit it. Closing this as wontfix.

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