From: Petter Reinholdtsen Date: Thu, 6 May 2010 21:29:53 +0000 (+0000) Subject: New entry. X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/ebb83a825cc50fc1badb7e829c4b929231ba5576?hp=0bfca3b9c82e95b306eb58737f021ddd42c3eae5 New entry. --- diff --git a/blog/data/2010-05-06-concurrent-boot.txt b/blog/data/2010-05-06-concurrent-boot.txt new file mode 100644 index 0000000000..2a1072feec --- /dev/null +++ b/blog/data/2010-05-06-concurrent-boot.txt @@ -0,0 +1,39 @@ +Title: Parallellizing the boot in Debian Squeeze - ready for wider testing +Tags: english, debian +Date: 2010-05-06 23:25 + +

These days, the init.d script dependencies in Squeeze are quite +complete, so complete that it is actually possible to run all the +init.d scripts in parallell based on these dependencies. If you want +to test your Squeeze system, make sure +dependency +based boot sequencing is enabled, and add this line to +/etc/default/rcS:

+ +
+CONCURRENCY=makefile
+
+ +

That is it. It will cause sysv-rc to use the startpar tool to run +scripts in parallel using the dependency information stored in +/etc/init.d/.depend.boot, /etc/init.d/.depend.start and +/etc/init.d/.depend.stop to order the scripts. Startpar is configured +to try to start the kdm and gdm scripts as early as possible, and will +start the facilities required by kdm or gdm as early as possible to +make this happen.

+ +

Give it a try, and see if you like the result. If some services +fail to start properly, it is most likely because they have incomplete +init.d script dependencies in their startup script (or some of their +dependent scripts have incomplete dependencies). Report bugs and get +the package maintainers to fix it. :)

+ +

Running scripts in parallel could be the default in Debian when we +manage to get the init.d script dependencies complete and correct. I +expect we will get there in Squeeze+1, if we get manage to test and +fix the remaining issues.

+ +

If you report any problems with dependencies in init.d scripts to +the BTS, please usertag the report to get it to show up at +the +list of usertagged bugs related to this