Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 77284 - rc launches scripts one-at-a-time that would be faster to start in parallel
rc launches scripts one-at-a-time that would be faster to start in parallel
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2002-11-04 12:43 EST by Benjamin Delfin
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-04 12:45:29 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch for rc file (2.82 KB, patch)
2002-11-04 12:45 EST, Benjamin Delfin
no flags Details | Diff

  None (edit)
Description Benjamin Delfin 2002-11-04 12:43:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)

Description of problem:
rc launches all kill and start scripts in /etc/rc.d/rc*.d one-at-a-time, 
waiting for each to finish.  By starting up all kill or start scripts with the 
same number (eg. 17 for S17xinetd) in the background, then waiting for all of 
them to finish, startup time can be cut.  There's no reason not to launch non-
network services while waiting for a network service to come up.  Careful 
tweaking to see which packages can be started in parallel will allow for 
significantly lower bootup times.

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

How reproducible:

Steps to Reproduce:
1. Boot Linux normally

Additional info:
Comment 1 Benjamin Delfin 2002-11-04 12:45:22 EST
Created attachment 83530 [details]
Patch for rc file
Comment 2 Bill Nottingham 2002-11-11 23:55:13 EST
A better solution would be to take actual dependencies into account; we'll
probably look towards doing something in that way in the future.

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