Package: cpufrequtils Version: 006-2 Tags: patch User: [email protected] Usertags: incorrect-dependency
I just did a test installation of Debian/Squeeze, and noticed the loadcpufreq init.d script is started before rsyslog. I tested to move it after the rsyslog service is operational, and running 'init.d/loadcpufreq start' during boot dod not cause the kernel to generate some syslog messages, nor did it generate any syslog messages itself. Can it generate syslog messages when something fail, or perhaps cause the system to crash and hang? If so, it might be a good idea to start it after the syslog collector is active. This patch will implement this. Not adding any stop dependencies, as the stop action is a no-op. --- cpufrequtils-006/debian/cpufrequtils.loadcpufreq.init 2010-04-21 14:43:08.000000000 +0200 +++ cpufrequtils-006-pere/debian/cpufrequtils.loadcpufreq.init 2010-04-21 14:43:32.000000000 +0200 @@ -1,7 +1,7 @@ #!/bin/sh ### BEGIN INIT INFO # Provides: loadcpufreq -# Required-Start: $remote_fs +# Required-Start: $remote_fs $syslog # Required-Stop: # Default-Start: 2 3 4 5 # Default-Stop: In any case, it should not harm to start a bit later during boot, so the patch should be safe to implement. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
