Bastian had some arguments against that approach: http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2011-December/003858.html
Jon Sent from my iPad On 17 Jan 2012, at 16:42, "Ritesh Raj Sarraf" <r...@debian.org> wrote: > On 01/17/2012 06:33 PM, Mike McClurg wrote: >> I think that we put a line in the xcp-xapi init script that quit >> without error if it found a xend pid file. This means that to start >> xapi you need to either 1) edit /etc/init.d/xend so that xend is never >> actually run, or 2) first let xend start, and then do 'service xend >> stop' to kill xend, and then do a 'service xcp-xapi start'. >> >> Neither of those is very attractive. Perhaps we could instead have the >> user create a /etc/default/xen file, which will contain a >> "TOOLSTACK=foo" line. If that file exists, and only if TOOLSTACK=xapi, >> we could then, within the xcp-xapi init script, check to see if xend >> is running, and if so, shut it down. This allows us to use xend as a >> common xen init script, but forces the user to explicitly say that >> they want to use xapi over xend. >> >> I would feel better about killing xend from within the xcp-xapi init >> file if we were to it this way. Thoughts? > > > You should just do all the stuff, that you expect from xend, inside > xcp-xapi. xend is a separate stack which will interest some users. > > Similarly, if xend is not really needed by xcp, I'd rather want to purge > it and only have xcp. > > -- > Ritesh Raj Sarraf | http://people.debian.org/~rrs > Debian - The Universal Operating System > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
