Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 18477

Summary: chkconfig --del and --add don't work with xinetd service
Product: [Retired] Red Hat Linux Reporter: Joshua Jensen <joshua>
Component: chkconfigAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: dr, rvokal
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: 2000-10-05 22:46:03 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 Joshua Jensen 2000-10-05 22:38:33 UTC
Not sure if this is a but or not:, but:

[root@joshua /root]# head -1 /etc/xinetd.d/telnet 
# default: on
[root@joshua /root]# grep disable /etc/xinetd.d/telnet
        disable = no
[root@joshua /root]# chkconfig --del telnet
[root@joshua /root]# grep disable /etc/xinetd.d/telnet
        disable = no
[root@joshua /root]# chkconfig --add telnet
[root@joshua /root]# grep disable /etc/xinetd.d/telnet
        disable = no

The man page for chkconfig doesn't mention xinetd services, so I'm not sure
if this is a bug or not.

I see that "chkconfig telnet on" works, even though using "on" without
--level should turn on a service in runlevels 3, 4, and 5.  Since --del and
--add work with the *defined* run-levels as specified by the " #chkconfig:"
lines in /etc/rc.d/init.d/ files, it should (IMHO) work for xinetd services
in simlary fashion (as defined by the "# default: on" line).

Comment 1 Bill Nottingham 2000-10-19 06:30:57 UTC
--add adds the default chkconfig links (i.e, S20foo, K80foo).
--del removes them.

Since there are no links to add/remove for xinetd services,
--add and --del don't do anything for them (similarly, since
xinetd doesn't keep track of runlevels, the --level directive
is ignored for xinetd services.)