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
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?
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:
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
Correct; chkconfig doesn't read xinetd.conf at all.
.rpmnew ignoring will be added in chkconfig-1.2.17-1.
Apparently fixed as of chkconfig-1.2.17-1 (RAWHIDE). If this is not the case please re-open this ticket.
Sorry, should have added that I manually enabled telnet/restarted xinetd and ran checkconfig to verify that it sees it as being on.
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.
Jonny, is this still an issue in today's chkconfig?
If not, Bill: will chkconfig be enhanced to read xinetd.conf too?
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.
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.