Bug 130240 - nifd service is not added using chkconfig during package installation.
Summary: nifd service is not added using chkconfig during package installation.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: howl
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC3Target
TreeView+ depends on / blocked
 
Reported: 2004-08-18 13:54 UTC by Alistair Riddoch
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-14 11:57:58 UTC


Attachments (Terms of Use)

Description Alistair Riddoch 2004-08-18 13:54:01 UTC
Description of problem:

nifd service is not added using chkconfig during package installation.

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

0.9.6-1

How reproducible:

Always.

Steps to Reproduce:
1. Install howl 0.9.6-1 from rpm.
2. Attempt to use chkconfig to view or control the nifd service.
3.
  
Actual results:

chkconfig does not know about nifd service.

Expected results:

chkconfig should be able to list the nifd service, and allow the
administrator to turn the service on or off.

Additional info:

Looking at the spec, it is clear that init scripts for both services
are installed in /etc/init.d, but chkconfig --add is only used on the
mDNSResponder service. In order for the nifd service to be available
to the standard service management tools, chkconfig --add should also
be used on the nifd service.

Comment 1 Alexander Larsson 2004-09-01 12:03:15 UTC
Its not installed because autoipd isn't really integrated into the os
yet (and i'm not sure yet exactly how to do this in the best way). So,
nifd isn't needed.

Comment 2 Alistair Riddoch 2004-09-01 12:40:47 UTC
It seems confusing for the init script to exist in /etc/rc.d/init.d
but not be registered using chkconfig. It seems like it would make more
sense for it to be registered, but default to off, or remove the
script from the package for the time being while it is not usable.

Comment 3 Alexander Larsson 2004-09-14 11:57:58 UTC
Fixed in 0.9.6-3


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