[Pkg-alsa-devel] Bug#375388: Incorrect boot order of alsa-utils and
sysklogd
Carlos Villegas
Carlos.Villegas at nuim.ie
Sun Jun 25 16:44:22 UTC 2006
Package: alsa-utils
Version: 1.0.11-4
alsa-utils script in the initscripts requires the metapackage $syslog
(i.e. sysklogd or syslog scripts) to start but it is ordered to start
before it. The reason for this is that S50alsa-utils is placed on the
/etc/rcS.d/ symbolic link pool while S10sysklogd is in /etc/rc2.d/.
$ less /etc/rcS.d/S50alsa-utils
....
# Required-Start: $syslog
...
$ ls /etc/rc2.d
...
S10sysklogd
...
I suggest that the script's symbolic link is placed on /etc/rc2.d
instead of /etc/rcS.d. Any order above 10 should do.
/etc/rc2.d/S15alsa-utils works for me. Besides, if lintian or linda
would report when dependency information is missing, it would be easier
to use a script adjust the order of the init scripts to ensure that
these are met for each system (as dependency information would be
available).
I am using Debian GNU/Linux Unstable, kernel 2.6.16-2-486
Carlos Villegas
More information about the Pkg-alsa-devel
mailing list