Bug 82935

Summary: kdenetwork does not chkconfig --add lisa init script
Product: [Retired] Red Hat Public Beta Reporter: Josiah Royse <jroyse>
Component: kdenetworkAssignee: Than Ngo <than>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: phoebe   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-29 15:14:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 79579    

Description Josiah Royse 2003-01-28 17:23:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030120

Description of problem:

The "lisa" init script is not "added" with chkconfig when installed.  The lisa
init script is missing from the "Service Configuration" app unless "chkconfig
--add lisa" is ran.  


The /etc/lisarc file is not customized to the user environment until the Lan
browsing wizard under the kcontrol panel is followed through, and a root
password is given to edit the /etc/lisarc file.  Then the dialog box reminds you
that lisa won't work until the init script is started.  By default the lisa init
script is always started when added to chkconfig:

# chkconfig: 2345 92 36
# description: LISa is a small daemon which is intended to run on \

Maybe it should be:

# chkconfig: - 92 36

until reminded to start it? With the first change it would be easy to start at
boot (if it shows up in Service Configuration app).

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


How reproducible:

Steps to Reproduce:
1.Look in the Service Configuration app for "lisa"

Actual Results:  not found

Expected Results:  to be there- preferably not starting under any runlevel... ?

Additional info:

Comment 1 Than Ngo 2003-01-29 15:14:10 UTC
it's fixed in 3.1-2