> This is probably the case. xenstored.service must be running before > xencommons.service. Since xencommons will start xenstored, we may not > need xenstored.service right?
It's useful to be able to disable xen guest launching on boot. disabling xendomains.service seems a logical way/place to do that. if not, &/or you remove it, what't the 'right' way to do it? -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
