Bug 52217 - wrong chkconfig line (with recent initscripts)
Summary: wrong chkconfig line (with recent initscripts)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: isdn4k-utils
Version: 1.0
Hardware: i386
OS: Linux
high
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-21 19:05 UTC by Ronny Buchmann
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-08-22 06:16:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Ronny Buchmann 2001-08-21 19:05:23 UTC
Description of Problem:
network configuration is loaded before isdn modules

Version-Release number of selected component (if applicable):
isdn4k-utils-3.1-44
initscripts-6.17-1

How Reproducible:
always

Steps to Reproduce:
boot with runlevel >=3

/etc/init.d/isdn is run after /etc/init.d/network, so ipppX devices dont work

Additional Information:
chkconfig for /etc/init.d/isdn should be "2345 09 91"
(network has "2345 10 90")

--- isdn.orig   Wed Aug  8 17:47:49 2001
+++ isdn        Tue Aug 21 21:06:04 2001
@@ -1,6 +1,6 @@
 #! /bin/bash
 #
-# chkconfig: 2345 24 89
+# chkconfig: 2345 09 91
 # description: start and stop ISDN services
 #

Comment 1 Ronny Buchmann 2001-08-22 06:15:56 UTC
but there comes a new serious problem:

if /usr is mounted over nfs, tools like isdnctrl arent avialable, so we must wait till /usr is mounted

i think the big problem is that initscripts load all network devices in one step, this is the wrong behaviour

it should load things in this order
1. setup network hardware not requiring things in /usr (eth, tr,...)
2. setup the devices for it
3. mount network filesystems
4. setup network hardware requiring stuff in /usr (isdn, xdsl)
5. setup the devices


Comment 2 Ngo Than 2001-08-22 09:26:27 UTC
It's fixed in isdn4k-utils-3.1-45. You will find it in next rawhide release.



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