Bug 204322 - wrong way to start deps
wrong way to start deps
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
: 209753 (view as bug list)
Depends On:
Blocks: FC7Target FC7Blocker
  Show dependency treegraph
Reported: 2006-08-28 10:56 EDT by David Zeuthen
Modified: 2013-03-05 22:46 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 20:46:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Zeuthen 2006-08-28 10:56:53 EDT
Description of problem:

NM calls "/sbin/service start dchcdbd", "/sbin/service start dchcdbd" form it's
start() method. This makes it, uhm,  pretty interesting when you change run
levels. Perhaps NM should also chkconfig --add those so they started / stopped
in the same runlevels as NM. Perhaps there's a better way though.

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

Comment 1 Matthias Clasen 2006-08-28 16:35:05 EDT
according to the initscripts maintainer, the fix for this is  "write an init
Comment 2 Matthias Clasen 2006-10-28 11:15:10 EDT
so, in rawhide, the "start dhcdbd" snipplet is gone from the NM  initscript,
with the consequence that NM does not work, unless you figure out that you have
to start dhcdbd manually :-(
Comment 3 Wade Mealing 2007-03-06 06:34:27 EST
*** Bug 209753 has been marked as a duplicate of this bug. ***
Comment 4 Bug Zapper 2008-04-03 14:03:13 EDT
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Comment 5 Bug Zapper 2008-05-06 20:46:55 EDT
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

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