Bug 63123 - chkconfig <svc> always return 1 for xinetd services
chkconfig <svc> always return 1 for xinetd services
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: chkconfig (Show other bugs)
rawhide
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Bill Nottingham
Ben Levenson
:
: 84316 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-04-10 06:07 EDT by Marco Lusini
Modified: 2014-03-16 22:26 EDT (History)
2 users (show)

See Also:
Fixed In Version: 1.3.14-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-02-02 16:45:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marco Lusini 2002-04-10 06:07:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
Using chkconfig to see if a xinetd service is configured to be started in the 
current runlevel always returns false. 

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


How reproducible:
Always

Steps to Reproduce:
1.chkconfig sendmail on
2.chkconfig telnet on
3.chkconfig sendmail ; echo $?
4.chkconfig telnet ; echo $?
	

Actual Results:  [root@iride mon]# chkconfig sendmail on
[root@iride mon]# chkconfig telnet on
[root@iride mon]# chkconfig sendmail ; echo $?
0
[root@iride mon]# chkconfig telnet ; echo $?
1


Expected Results:  [root@iride mon]# chkconfig sendmail on
[root@iride mon]# chkconfig telnet on
[root@iride mon]# chkconfig sendmail ; echo $?
0
[root@iride mon]# chkconfig telnet ; echo $?
0


Additional info:
Comment 1 Ben Levenson 2002-04-10 11:55:50 EDT
verified. should 'chkconfig <xinetd service>' look in /etc/xinetd.d/<service>
for the appropriate info? It appears to only check /etc/rc[0-6].d/
Comment 2 Bill Nottingham 2003-02-14 10:09:51 EST
*** Bug 84316 has been marked as a duplicate of this bug. ***
Comment 3 Bill Nottingham 2005-02-02 16:45:54 EST
Fixed in 1.3.14-1.

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