Re: update-rc.d and rare start/stop runlevels
On 2011-01-27 14:20 +0100, Mats Erik Andersson wrote:
> torsdag den 27 januari 2011 klockan 10:45 skrev Sven Joachim detta:
>> On 2011-01-27 00:11 +0100, Mats Erik Andersson wrote:
>>
>> > onsdag den 26 januari 2011 klockan 16:59 skrev Boyd Stephen Smith Jr. detta:
>> >>
>> >> How are you calling update-rc.d? These warning messages indicate to me that
>> >> update-rc.d is complaining that you've asked it to install S* links in
>> >> rc{2,3,4,5}.d and K* links in rc{0,1,6}.d but that the init script expects
>> >> something different, namely what you've listed in the script.
>> >
>> > It is done in the postinst script, automatically created by debhelper:
>> >
>> > update-rc.d downtimed defaults >/dev/null
>> >
>> > I have not manipulated that part. Should I craft a suitable override_dh_*
>> > to achive the correct scripting?
>>
>> Yes, you need the -u option in dh_installinit(1).
>
> A great observation and reminder! Using
>
> override_dh_installinit:
> dh_installinit -- start 21 S . stop 07 0 6 .
>
> in the rules file, the warnings disappear, but on my dependency booted
> system the priorities were still set to K01 and S20 thereby ignoring
> my wish.
The numbers of the KNN and SNN symlinks on your system are computed on
the fly by insserv, that's the whole point of the dependency based boot
system. Only the legacy order uses the numbers that you supply to
update-rc.d.
Sven
Reply to: