Bug#20373: PROPOSED] shouldn't start init scripts in wrong runlevel

[Edward Betts <edward@debian.org>]

On policy, Piotr Roszatycki <dexter@fnet.pl> wrote:
> > (That is, we should check whether /etc/rcN.d/{S,K}??script exists
> > where N is the current runlevel and start or stop the script
> > appropriately if it does -- see the rest of this bugreport for
> > details.)
> > 
> > I second this proposal.
> 
> I'm using file-rc package. There is no /etc/rc?.d directories on my Debian
> system. I've got only /etc/runleves.conf file in place of these dirs.
> 
> The Debian Policy doesn't require to exist /etc/rc?.d directories.

This could get very ugly/messy. I think it wants a script/program to be part
of dpkg that when passed a /etc/init.d script and an action will check the
current run level and the /etc/rc?.d dirs or /etc/runleves.conf and run the
right script if needed. As I said messy. We want the logic to be in a seperate
program and not in EVERY {post,pre}{inst,rm} script that plays with
/etc/init.d/* files.

Is there some way to make initd think it has just re-entered the current run
level and so force the appropriate run-level scripts to run? Maybe I am thinking
about this the wrong way.

What about the ordering in /etc/rc?.d is it important, should we not be
restarting stuff out of order?

-- 
I consume, therefore I am