Package: insserv
Version: 1.14.0-2
Severity: normal

>From /usr/share/doc/insserv/README.Debian:

An experimental feature to run init.d scripts in parallel is also
available.  Use the CONCURRENCY setting in /etc/default/rcS to
enable it.

In short:

  # Enable parallel booting
  echo CONCURRENCY=makefile >> /etc/default/rcS

....

The 'makefile' style concurrency depend on complete and correct
dependencies in all init.d scripts.  There is a simpler and less
strict style 'startpar'

This conflicts with /etc/init.d/rc from sysv-rc 2.88dsf-13:

# Specify method used to enable concurrent init.d scripts.
# Valid options are 'none' and 'makefile'.  Obsolete options
# used earlier are 'shell' and 'startpar'.  The obsolete options
# are aliases for 'makefile' since 2010-05-14.  The default since
# the same date is 'makefile', as the init.d scripts in Debian now
# include dependency information and are ordered using this
# information.  See insserv for information on dependency based
# boot sequencing.
CONCURRENCY=makefile

I think that sysv-rc is right: it boots parallel by default
(when possible), and regards startpar as an obsolete alias 
for makefile.  Therefore please update the README file.

The Debian Release Notes, Section 2.1.2 is also wrong about
parallel booting not enabled by default.  If you agree I will file a bug 
report aginst it.

-- System Information:
Debian Release: squeeze/sid
  APT prefers stable
  APT policy: (990, 'stable'), (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages insserv depends on:
ii  libc6                         2.11.2-7   Embedded GNU C Library: Shared lib

insserv recommends no packages.

Versions of packages insserv suggests:
pn  bootchart                     <none>     (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to