Quoting Stéphane Graber ([email protected]): > On Thu, May 01, 2014 at 05:14:12PM -0400, Michael H. Warfield wrote: > > Related to this... Dwight and I have been bouncing a couple of things > > back and forth and I noticed that lxc-autostart is being called from the > > sysvinit scripts without the -a parameter. That means that any > > container in a non-null group will not be autostart on boot. I feel > > that's the wrong behavior. If autoboot = 1 then it should be autobooted > > on boot. What you do after boot is up to you but I would expect it to > > be "autoboot = 1" => "autobooted on bootup", not "autoboot = 1" => > > "autobooted on bootup if it's not in a group". > > I can see why you'd auto-start both the null group and say a "boot" > group, but I don't think we should auto-start them all. > > A reason is that I use those groups as a way to easily start a group of > interdependent containers, when I need those, I do "lxc-autostart -g > blah" and all containers that have lxc.group = blah and lxc.start.auto = > 1 will start properly sorted, with the right delays, ...). I however > don't necessarily want those to start at boot.
And... do you have containers in lxc.cgroup = blah which you do not want to have started when you do lxc-autostart -g blah? _______________________________________________ lxc-devel mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-devel
