On Fri, Oct 31, 2008 at 11:46 PM, Ovidiu Rosoiu
<email address hidden> wrote:
> Actually now my startup config is:
>
> /etc/rc0.d/K01kdm
> /etc/rc1.d/K01kdm
> /etc/rc2.d/S99kdm
> /etc/rc3.d/S99kdm
> /etc/rc4.d/S99kdm
> /etc/rc5.d/S99kdm
> /etc/rc6.d/K01kdm
>
> which I had to set mannualy, because an `update-rc.d kdm defaults` would
> set kdm start scripts at priority 20, lower than hal. Setting the
> priority manually fixes the problem.
I did something similar, also by hand. Strictly speaking I think the
K links should also be at 99, because they're run in reverse order.
But precise shutdown order is a bit moot.
On Fri, Oct 31, 2008 at 11:46 PM, Ovidiu Rosoiu
<email address hidden> wrote:
> Actually now my startup config is:
>
> /etc/rc0.d/K01kdm
> /etc/rc1.d/K01kdm
> /etc/rc2.d/S99kdm
> /etc/rc3.d/S99kdm
> /etc/rc4.d/S99kdm
> /etc/rc5.d/S99kdm
> /etc/rc6.d/K01kdm
>
> which I had to set mannualy, because an `update-rc.d kdm defaults` would
> set kdm start scripts at priority 20, lower than hal. Setting the
> priority manually fixes the problem.
I did something similar, also by hand. Strictly speaking I think the
K links should also be at 99, because they're run in reverse order.
But precise shutdown order is a bit moot.
-- launchpad. net/~mbp/>
Martin <http://