Your message dated Sun, 16 May 2010 19:28:15 +0200
with message-id <20100516172815.ga3...@login2.uio.no>
and subject line Re: Bug#581766: update-rc.d: seems to give incorrect warnings
has caused the Debian Bug report #581766,
regarding update-rc.d: seems to give incorrect warnings
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
581766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-4
Severity: minor
Hi.
Not sure whether I misunderstand something here, but when I do e.g. the
following...:
# update-rc.d cpufrequtils defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: cpufrequtils stop runlevel arguments (0 1 6) do not match
LSB Default-Stop values (none)
# update-rc.d loadcpufreq defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: loadcpufreq stop runlevel arguments (0 1 6) do not match
LSB Default-Stop values (none)
(The same happens with other init scripts (e.g. mcelog), too.)
..I get these warnings that the stop levels wouldn't match, however:
# l /etc/rc*.d/*cpufreq*
lrwxrwxrwx 1 root root 21 May 15 19:16 /etc/rc2.d/S23loadcpufreq ->
../init.d/loadcpufreq
lrwxrwxrwx 1 root root 22 May 15 19:16 /etc/rc2.d/S24cpufrequtils ->
../init.d/cpufrequtils
lrwxrwxrwx 1 root root 21 May 15 19:16 /etc/rc3.d/S23loadcpufreq ->
../init.d/loadcpufreq
lrwxrwxrwx 1 root root 22 May 15 19:16 /etc/rc3.d/S24cpufrequtils ->
../init.d/cpufrequtils
lrwxrwxrwx 1 root root 21 May 15 19:16 /etc/rc4.d/S23loadcpufreq ->
../init.d/loadcpufreq
lrwxrwxrwx 1 root root 22 May 15 19:16 /etc/rc4.d/S24cpufrequtils ->
../init.d/cpufrequtils
lrwxrwxrwx 1 root root 21 May 15 19:16 /etc/rc5.d/S23loadcpufreq ->
../init.d/loadcpufreq
lrwxrwxrwx 1 root root 22 May 15 19:16 /etc/rc5.d/S24cpufrequtils ->
../init.d/cpufrequtils
There are no stop symlinks at 0, 1 or 6?
Is this a bug?
Cheers,
Chris.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.33-heisenberg (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages sysv-rc depends on:
ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii insserv 1.14.0-2 Tool to organize boot sequence usi
ii sysvinit-utils 2.88dsf-4 System-V-like utilities
Versions of packages sysv-rc recommends:
ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip
Versions of packages sysv-rc suggests:
pn bum <none> (no description available)
ii sysv-rc-conf 0.99-6 SysV init runlevel configuration t
-- debconf information:
sysv-rc/unable-to-convert:
sysv-rc/convert-legacy: true
--- End Message ---
--- Begin Message ---
The lack of reply make me suspect my last posting provided the
information needed to clear out the misunderstanding regarding
update-rc.d behaviour, so I close this report as fixed.
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
