Bug#20373: PROPOSED] shouldn't start init scripts in wrong runlevel
- To: 20373@bugs.debian.org
- Subject: Bug#20373: PROPOSED] shouldn't start init scripts in wrong runlevel
- From: Edward Betts <edward@debian.org>
- Date: Mon, 31 May 1999 19:35:42 +0100
- Message-id: <19990531193542.C2096@portaloo.>
- Reply-to: Edward Betts <edward@debian.org>, 20373@bugs.debian.org
- In-reply-to: <E10oFij-0002IR-00@polya>; from Julian Gilbey on Mon, May 31, 1999 at 01:14:25AM +0100
- References: <19990531001150.C3769@portaloo.> <E10oFij-0002IR-00@polya>
On policy, Julian Gilbey <J.D.Gilbey@qmw.ac.uk> wrote:
> > What about the ordering in /etc/rc?.d is it important, should we not be
> > restarting stuff out of order?
>
> I would guess not; these are not facilities being restarted but newly
> installed ones. If there is a desperate problem with this, it should
> be dealt with by a Depends: mechanism or the like.
And packages that have been upgraded. In an upgrade from hamm -> slink all of
/etc/init.d will have to be stopped and started. Althought, I must admit that
I think the order is probably not that important.
--
I consume, therefore I am
Reply to: