On 01/17/2012 07:49 AM, Jonathan Ludlam wrote: > I actually ran into a problem very similar to this myself this morning - it > came from the fact that the init scripts were reordered at some point, and I > still had the old init script ordering. > > I sorted it temporarily by starting the scripts by hand - the normal order is: > > 20: xcp-fe, xend, xcp-v6d > 22: xcp-squeezed > 23: xcp-xapi
Did you have this issue in Debian SID? It'd be very surprising, because for init.d scripts, we have: # Provides: xcp-xapi # Required-Start: $remote_fs $syslog xcp-squeezed xcp-v6d xcp-fe # Required-Stop: $remote_fs $syslog # Provides: xcp-squeezed # Required-Start: $remote_fs $syslog xend # Required-Stop: $remote_fs $syslog So, to me, your issue maybe have been that the xcp-squeezed init.d script should also depend on xcp-fe and xcp-v6d. Should I patch the xen-api package in this way? Or is it not important that xcp-fe and xcp-v6d starts before xcp-squeezed? Also note that if I do the above changes to the init.d script of xcp-squeezed, we will have to add dependencies at the package level, so that xcp-squeezed depends on xcp-fe and xcp-v6d. Otherwise, we'll have piuparts failure like when xcp-xapi didn't depend on xen-utils-common. Please let me know, Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
