Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 77921 - serviceconf does not display correctly all services that you can see with chkconfig
Summary: serviceconf does not display correctly all services that you can see with chk...
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: serviceconf
Version: 7.3
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-15 12:56 UTC by ab
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-11-15 12:56:25 UTC

Attachments (Terms of Use)

Description ab 2002-11-15 12:56:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 

Description of problem:
I have added 3 new services through the chkconfig utility, unfortuantely one of 
those (bundle_processor) cannot be displayed by the serviceconf utility. I 
suppose because of the "tab" indentation of the service that has got a name 
longer than the others as you can see below:
 grabber         0:off 1:off 2:off 3:on 4:on 5:on 6:off
 bundle_processor 0:off 1:off 2:off 3:on 4:on 5:on 6:off
 listener        0:off 1:off 2:off 3:on 4:on 5:on 6:off

It seems to be a parsing failure on that.

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

How reproducible:

Steps to Reproduce:
1.add a service named bundle_processor (or longer name) through chkconfig 

Actual Results:  il will be displayed by the chkconfig --list correctly
il will not be displyed at all by the serviceconf

Expected Results:  serviceconf should have displayed all the services that 
chkconfig utility lists

Additional info:

Comment 1 Daniel Walsh 2002-11-15 14:57:14 UTC
This bug has been fixed in the current release.  It is available in 8.0

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