Bug 82935 - kdenetwork does not chkconfig --add lisa init script
kdenetwork does not chkconfig --add lisa init script
Status: CLOSED RAWHIDE
Product: Red Hat Public Beta
Classification: Retired
Component: kdenetwork (Show other bugs)
phoebe
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
:
Depends On:
Blocks: 79579
  Show dependency treegraph
 
Reported: 2003-01-28 12:23 EST by Josiah Royse
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-29 10:14:10 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 Josiah Royse 2003-01-28 12:23:58 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030120

Description of problem:
First:

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.  

Second:

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):

kdenetwork-3.1-0.9

How reproducible:
Always

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

Actual Results:  not found

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

Additional info:
Comment 1 Ngo Than 2003-01-29 10:14:10 EST
it's fixed in 3.1-2

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