On Thu, 10 Mar 2005, Miquel van Smoorenburg wrote: > On Wed, 9 Mar 2005, Adam Heath wrote: > >On Wed, 9 Mar 2005, Adam Heath wrote: > >>On Wed, 9 Mar 2005, Henning Glawe wrote: > >>> > >>> Moin, > >>> just discovered a small problem in the xen-debian packages (2.0.4-4, from > >>> people.d.o): > >>> the sysv init links are done in the following way: > >>> > >>> S20xend > >>> S20xendomains > >>> K20xend > >>> K20xendomains > >>> > >>> so xend is shutdown before the xen-domains are shutdown, which of cause > >>> fails > >>> when there's no xend... > > > >>This is a bug in run-parts. It should reverse the order. > >> > >>Or you are not understanding how it works. > > > >reassign 298783 sysv-rc > >thanks > > I don't understand. What is the bug? The order sysv-rc uses to > run the scripts is the standard order used by POSIX when you > do a "for i in S??*". That is well known. If that isn't what > you'd like it to be, fix the priority of the Sxx symlinks. > > Or am I overlooking something ?
Hrm. Maybe this is a problem with update-rc.d. But I don't know. update-rc.d defaults bar creates rc2.d/S20bar and rc6.d/K20bar, and update-rc.d defaults foo creates rc2.d/S20foo and rc6.d/K20foo. During start, bar is started before foo, which is what is expected. However, during shutdown, bar is stopped *before* foo, instead of the other way around. Yes, one can change the priority of one of the scripts. But that is a lot more overhead. I'm cc'ing devel, as this could be a more general problem, worthy of a broader fix. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
