Re: [lxc-users] How to cancel lxc-autostart
On Sat, 2014-08-09 at 11:02 -0400, CDR wrote: > That is correct, but why not a command called "lxc-cancelautostart"? Unnecessary. > It seems obvious. Not really. Not other solutions exist. Regards, Mike > On Sat, Aug 9, 2014 at 10:57 AM, Tom Weber > wrote: > > Everything is there already. Even in real world. > > you could: > > - define a run level for this purpose > > - delay the autostart > > - run your own script during bootup which asks you wether it should kick > > off the lxc-autostart process or not - it might default to yes after a > > timeout if no input occurs > > - create your own script which would check the grub commandline for a > > nolxcstartup parameter > > ... > > > > there are plenty of ways which are way better than firing a bullet and > > then requesting a feature to cancel it. > > All of them are rather trivial to implement. Any professional admin to > > host 300 containers should be able to do it. Yet you don't seem to even > > have tried any of these solutions. > > > > Tom > > > > Am Samstag, den 09.08.2014, 10:32 -0400 schrieb CDR: > >> This is a philosophical divide. I live in the real world, and are > >> successfully moving all my business to LXC, or a combination of LXC > >> and real virtualization, where you have a few virtual machines with > >> hundreds of GBs of RAM and 36 or more cores, and these super-virtual > >> machines act solely as container-of-containers. It means that my > >> virtual machines have so many autostart containers, that it takes 30 > >> minutes to stop them all in a loop. When for some reason I need to > >> start the machines and do not need all the containers starting, the > >> only way is to boot in single-user mode. Why? There should be way to > >> stop the storm in its tracks, like > >> cat 0 > /proc/lxc/autostart > >> this way I could quickly stop the few containers that had already started. > >> I see a world coming where every living corporation will be using a > >> combination of Virtualization plus LXC. > >> Philip > >> > >> > >> On Sat, Aug 9, 2014 at 8:27 AM, brian mullan > >> wrote: > >> > I've been reading this thread and this is the first and only time I've > >> > ever > >> > heard anyone request such a "kill all" command for LXC to terminate > >> > auto-start. > >> > > >> > Developer time is always in short supply and IMHO asking one of them to > >> > spend their time on such a "corner-case" issue is not putting their > >> > efforts > >> > to good use. > >> > > >> > There have been 2 alternatives proposed that seem would handle this event > >> > and my opinion is that should be sufficient. > >> > > >> > LXC 1.x has a lot of important work going on and I'd rather see people > >> > focused on the existing roadmap or on addressing critical bugs. > >> > > >> > Of course its all Open Source so anyone that can't live without such a > >> > feature could either contribute the patches themselves or offer a bounty > >> > to > >> > have it done for them. > >> > > >> > again just my opinion > >> > > >> > Brian > >> > > >> > > >> > ___ > >> > lxc-users mailing list > >> > lxc-users@lists.linuxcontainers.org > >> > http://lists.linuxcontainers.org/listinfo/lxc-users > >> ___ > >> lxc-users mailing list > >> lxc-users@lists.linuxcontainers.org > >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > > > > ___ > > lxc-users mailing list > > lxc-users@lists.linuxcontainers.org > > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > -- Michael H. Warfield (AI4NB) | (770) 978-7061 | m...@wittsend.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it! signature.asc Description: This is a digitally signed message part ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
Third solution proposal near bottom. Sorry for longish post, but... On Sat, 2014-08-09 at 10:32 -0400, CDR wrote: > This is a philosophical divide. I live in the real world, and are > successfully moving all my business to LXC, or a combination of LXC > and real virtualization, where you have a few virtual machines with > hundreds of GBs of RAM and 36 or more cores, and these super-virtual > machines act solely as container-of-containers. It means that my > virtual machines have so many autostart containers, that it takes 30 > minutes to stop them all in a loop. When for some reason I need to > start the machines and do not need all the containers starting, the > only way is to boot in single-user mode. Why? There should be way to > stop the storm in its tracks, like > cat 0 > /proc/lxc/autostart > this way I could quickly stop the few containers that had already started. > I see a world coming where every living corporation will be using a > combination of Virtualization plus LXC. OK, if we're going to get into it, I also live in the real world where I put these things to practical uses and I look for practical answers to practical questions. I have several colocated servers across multiple and several isolated servers with a number of containers on each. I control and manage a large span (/16) of IPv4 address space and I peer live on BGP using my own ASN (25944) for both IPv4 and IPv6 advertising my own real global address space. I'm even the author of some of the BGP code in the Quagga routing suite (MD5 TCP signature code). Yes, I think I qualify as a practical, real world, engineer who has been in practice and solving problems for well over 30 years at this point. You posited an unlikely condition. The case where you had to stop lxc-autostart in order to fsck a file system for a container. But, how did the file system get mounted dirty? That should not happen. Sounds like that indicates other underlying problems. If the file system did not get mounted, that phase should have aborted anyways unless it was somehow miss-engineered in the first place. If it's a container specific failure, you can fix that container problem without shutting down all the other containers and if it's a generic problem, the other affected containers should not have started either. We (I and one other) gave you practical solutions to the problem you posited but apparently wasn't the answer you have envisioned. We also foresaw problems with your "solution" which you obviously had not. You haven't countered either of the proposed solutions with reasons why they would not work or offered any more "real world" examples on which we could base and analysis. From the description of what you've provided above, the "where you have a few virtual machines with hundreds of GBs of RAM and 36 or more cores, and these super-virtual machines act solely as container-of-containers", it sounds like you're just designing this thing and much of this is theoretical. It also sounds like, in the case you're describing now, you need to apply some higher level management and some serious addressing of container groups. This is exactly one of the cases I envision when I was working on lxc-autostart and the whole group model, multiple group membership and boot order/priority. To manage things on that level, you're going to need a higher level of management and not just a shot-gun to fire back at the stream of bullets. In that case, you're going to need a well documented, stepped, incremental, and grouped approach to that multitude of containers-of-containers. Yes, you're dealing with exactly the load average and real-time delays inherent in that level of complexity. I doubt any solution is capable of fully addressing that. In the container-of-containers case, you're also going to need some level (on bootup) of cross container coordination (allow one container to boot it's containers after another container has completed it's boot?). I especially don't know how you would expect an lxc-autostart abort to behave in that case. You're not going to get it to shut down all the containers running lxc-autostart. This is a morass and you're going to need a firmly ordered approach, as opposed to a shotgun approach. As a practical, real world, engineer, I don't always get the answer I would like (for one reason or another) but I do generally get my problems solved (sometimes in ways I hadn't thought of that were significantly better - lxc-autostart is head and shoulders better than the lxc-run script I was using internally and never proposed). I usually get further by asking "how do I solve this scenario" rather than say "We like toast, make it make toast" (an actual comment I heard at an IETF Conference where I was talking with one of the WG chairs complaining about a certain faction within his WG and their personal proposal that he wanted my opinion on - names of the guilty shall not be revealed). Bottom line is that you have yet to
Re: [lxc-users] How to cancel lxc-autostart
because everything you need is already there.. you request a feature noone needs and that you can implement yourself already... another approach: man lxc.container.conf(5) see lxc.hook.pre-start make that script check for /tmp/lxcdontautostart and bail out if it exists. Tom Am Samstag, den 09.08.2014, 11:02 -0400 schrieb CDR: > That is correct, but why not a command called "lxc-cancelautostart"? > It seems obvious. > > > On Sat, Aug 9, 2014 at 10:57 AM, Tom Weber > wrote: > > Everything is there already. Even in real world. > > you could: > > - define a run level for this purpose > > - delay the autostart > > - run your own script during bootup which asks you wether it should kick > > off the lxc-autostart process or not - it might default to yes after a > > timeout if no input occurs > > - create your own script which would check the grub commandline for a > > nolxcstartup parameter > > ... > > > > there are plenty of ways which are way better than firing a bullet and > > then requesting a feature to cancel it. > > All of them are rather trivial to implement. Any professional admin to > > host 300 containers should be able to do it. Yet you don't seem to even > > have tried any of these solutions. > > > > Tom > > > > Am Samstag, den 09.08.2014, 10:32 -0400 schrieb CDR: > >> This is a philosophical divide. I live in the real world, and are > >> successfully moving all my business to LXC, or a combination of LXC > >> and real virtualization, where you have a few virtual machines with > >> hundreds of GBs of RAM and 36 or more cores, and these super-virtual > >> machines act solely as container-of-containers. It means that my > >> virtual machines have so many autostart containers, that it takes 30 > >> minutes to stop them all in a loop. When for some reason I need to > >> start the machines and do not need all the containers starting, the > >> only way is to boot in single-user mode. Why? There should be way to > >> stop the storm in its tracks, like > >> cat 0 > /proc/lxc/autostart > >> this way I could quickly stop the few containers that had already started. > >> I see a world coming where every living corporation will be using a > >> combination of Virtualization plus LXC. > >> Philip > >> > >> > >> On Sat, Aug 9, 2014 at 8:27 AM, brian mullan > >> wrote: > >> > I've been reading this thread and this is the first and only time I've > >> > ever > >> > heard anyone request such a "kill all" command for LXC to terminate > >> > auto-start. > >> > > >> > Developer time is always in short supply and IMHO asking one of them to > >> > spend their time on such a "corner-case" issue is not putting their > >> > efforts > >> > to good use. > >> > > >> > There have been 2 alternatives proposed that seem would handle this event > >> > and my opinion is that should be sufficient. > >> > > >> > LXC 1.x has a lot of important work going on and I'd rather see people > >> > focused on the existing roadmap or on addressing critical bugs. > >> > > >> > Of course its all Open Source so anyone that can't live without such a > >> > feature could either contribute the patches themselves or offer a bounty > >> > to > >> > have it done for them. > >> > > >> > again just my opinion > >> > > >> > Brian > >> > > >> > > >> > ___ > >> > lxc-users mailing list > >> > lxc-users@lists.linuxcontainers.org > >> > http://lists.linuxcontainers.org/listinfo/lxc-users > >> ___ > >> lxc-users mailing list > >> lxc-users@lists.linuxcontainers.org > >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > > > > ___ > > lxc-users mailing list > > lxc-users@lists.linuxcontainers.org > > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
That is correct, but why not a command called "lxc-cancelautostart"? It seems obvious. On Sat, Aug 9, 2014 at 10:57 AM, Tom Weber wrote: > Everything is there already. Even in real world. > you could: > - define a run level for this purpose > - delay the autostart > - run your own script during bootup which asks you wether it should kick > off the lxc-autostart process or not - it might default to yes after a > timeout if no input occurs > - create your own script which would check the grub commandline for a > nolxcstartup parameter > ... > > there are plenty of ways which are way better than firing a bullet and > then requesting a feature to cancel it. > All of them are rather trivial to implement. Any professional admin to > host 300 containers should be able to do it. Yet you don't seem to even > have tried any of these solutions. > > Tom > > Am Samstag, den 09.08.2014, 10:32 -0400 schrieb CDR: >> This is a philosophical divide. I live in the real world, and are >> successfully moving all my business to LXC, or a combination of LXC >> and real virtualization, where you have a few virtual machines with >> hundreds of GBs of RAM and 36 or more cores, and these super-virtual >> machines act solely as container-of-containers. It means that my >> virtual machines have so many autostart containers, that it takes 30 >> minutes to stop them all in a loop. When for some reason I need to >> start the machines and do not need all the containers starting, the >> only way is to boot in single-user mode. Why? There should be way to >> stop the storm in its tracks, like >> cat 0 > /proc/lxc/autostart >> this way I could quickly stop the few containers that had already started. >> I see a world coming where every living corporation will be using a >> combination of Virtualization plus LXC. >> Philip >> >> >> On Sat, Aug 9, 2014 at 8:27 AM, brian mullan wrote: >> > I've been reading this thread and this is the first and only time I've ever >> > heard anyone request such a "kill all" command for LXC to terminate >> > auto-start. >> > >> > Developer time is always in short supply and IMHO asking one of them to >> > spend their time on such a "corner-case" issue is not putting their efforts >> > to good use. >> > >> > There have been 2 alternatives proposed that seem would handle this event >> > and my opinion is that should be sufficient. >> > >> > LXC 1.x has a lot of important work going on and I'd rather see people >> > focused on the existing roadmap or on addressing critical bugs. >> > >> > Of course its all Open Source so anyone that can't live without such a >> > feature could either contribute the patches themselves or offer a bounty to >> > have it done for them. >> > >> > again just my opinion >> > >> > Brian >> > >> > >> > ___ >> > lxc-users mailing list >> > lxc-users@lists.linuxcontainers.org >> > http://lists.linuxcontainers.org/listinfo/lxc-users >> ___ >> lxc-users mailing list >> lxc-users@lists.linuxcontainers.org >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
Everything is there already. Even in real world. you could: - define a run level for this purpose - delay the autostart - run your own script during bootup which asks you wether it should kick off the lxc-autostart process or not - it might default to yes after a timeout if no input occurs - create your own script which would check the grub commandline for a nolxcstartup parameter ... there are plenty of ways which are way better than firing a bullet and then requesting a feature to cancel it. All of them are rather trivial to implement. Any professional admin to host 300 containers should be able to do it. Yet you don't seem to even have tried any of these solutions. Tom Am Samstag, den 09.08.2014, 10:32 -0400 schrieb CDR: > This is a philosophical divide. I live in the real world, and are > successfully moving all my business to LXC, or a combination of LXC > and real virtualization, where you have a few virtual machines with > hundreds of GBs of RAM and 36 or more cores, and these super-virtual > machines act solely as container-of-containers. It means that my > virtual machines have so many autostart containers, that it takes 30 > minutes to stop them all in a loop. When for some reason I need to > start the machines and do not need all the containers starting, the > only way is to boot in single-user mode. Why? There should be way to > stop the storm in its tracks, like > cat 0 > /proc/lxc/autostart > this way I could quickly stop the few containers that had already started. > I see a world coming where every living corporation will be using a > combination of Virtualization plus LXC. > Philip > > > On Sat, Aug 9, 2014 at 8:27 AM, brian mullan wrote: > > I've been reading this thread and this is the first and only time I've ever > > heard anyone request such a "kill all" command for LXC to terminate > > auto-start. > > > > Developer time is always in short supply and IMHO asking one of them to > > spend their time on such a "corner-case" issue is not putting their efforts > > to good use. > > > > There have been 2 alternatives proposed that seem would handle this event > > and my opinion is that should be sufficient. > > > > LXC 1.x has a lot of important work going on and I'd rather see people > > focused on the existing roadmap or on addressing critical bugs. > > > > Of course its all Open Source so anyone that can't live without such a > > feature could either contribute the patches themselves or offer a bounty to > > have it done for them. > > > > again just my opinion > > > > Brian > > > > > > ___ > > lxc-users mailing list > > lxc-users@lists.linuxcontainers.org > > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
This is a philosophical divide. I live in the real world, and are successfully moving all my business to LXC, or a combination of LXC and real virtualization, where you have a few virtual machines with hundreds of GBs of RAM and 36 or more cores, and these super-virtual machines act solely as container-of-containers. It means that my virtual machines have so many autostart containers, that it takes 30 minutes to stop them all in a loop. When for some reason I need to start the machines and do not need all the containers starting, the only way is to boot in single-user mode. Why? There should be way to stop the storm in its tracks, like cat 0 > /proc/lxc/autostart this way I could quickly stop the few containers that had already started. I see a world coming where every living corporation will be using a combination of Virtualization plus LXC. Philip On Sat, Aug 9, 2014 at 8:27 AM, brian mullan wrote: > I've been reading this thread and this is the first and only time I've ever > heard anyone request such a "kill all" command for LXC to terminate > auto-start. > > Developer time is always in short supply and IMHO asking one of them to > spend their time on such a "corner-case" issue is not putting their efforts > to good use. > > There have been 2 alternatives proposed that seem would handle this event > and my opinion is that should be sufficient. > > LXC 1.x has a lot of important work going on and I'd rather see people > focused on the existing roadmap or on addressing critical bugs. > > Of course its all Open Source so anyone that can't live without such a > feature could either contribute the patches themselves or offer a bounty to > have it done for them. > > again just my opinion > > Brian > > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
I've been reading this thread and this is the first *and only time* I've ever heard anyone request such a "kill all" command for LXC to terminate auto-start. Developer time is always in short supply and IMHO asking one of them to spend their time on such a *"corner-case" issue* is not putting their efforts to good use. There have been 2 alternatives proposed that seem would handle this event and my opinion is that should be sufficient. LXC 1.x has a lot of important work going on and I'd rather see people focused on the existing roadmap or on addressing critical bugs. Of course its all Open Source so anyone that can't live without such a feature could either contribute the patches themselves or offer a bounty to have it done for them. again just my opinion Brian ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
On Fri, Aug 08, 2014 at 07:04:58PM -0400, CDR wrote: > Correct. It is a "cancel fire bullet". I want to ask the developers to > create a new command that would do this. If you are asking about an automatic solution, it would help to know in which cases you want a container (or a group) to _not_ start (the fsck example doesn't make sense because a dedicated lxc partition would be fsck'ed on-boot). In principle, you can go as wild as you want. For example, you can start containers only iff a particular USB stick is inserted (this can be straightforwardly done with systemd, but you'll have to hook into udev on an upstart machine)... Cheers, -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D pgpORlnPS8Rv1.pgp Description: PGP signature ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
On Fri, 2014-08-08 at 19:04 -0400, CDR wrote: > Correct. It is a "cancel fire bullet". I want to ask the developers to > create a new command that would do this. So far, I don't see anything you have suggested that can't be solved using either the runlevel method or the delayed alternate boot group method. Both would be far more reliable and deterministic. You'll be far better off not using the default boot group (i.e. either NULL or onboot) and delaying the initial startup until after you are sure you don't need to intervene. The advantage, in my mind, with the alternate delayed boot group is that you could, as I do, prioritize certain containers that must be started (like DNS servers) while others could be deferred. The deferred ones could be started out of a cron job with triggers and/or delays by re-invoking lxc-autostart with the alternate boot group. Once this process is started, though, if you were to stop it, you could have some containers started and some not started and some in-between. Regards, Mike > On Fri, Aug 8, 2014 at 5:48 PM, Tom Weber > wrote: > > define a runlevel where the containers are not started or boot in single > > user mode and modify the start script. > > > > that cancel mechanism you ask for is like a 'cancel fired bullet' button > > for a gun. > > > > Tom > > > > Am Freitag, den 08.08.2014, 16:50 -0400 schrieb CDR: > >> After I reboot, the LXC service will start automatically all the > >> containers marked for auto-start. I have not found a way to stop that > >> mechanism if I absolutely need that the containers to not start. > >> Suppose I need to umount the partition to issue an "fsck", etc. How do > >> I preempt the automatic behavior? > >> It is something like the Iron Dome. Hundreds of containers are on the > >> air and will be started, how do you override this behavior? > >> > >> On Fri, Aug 8, 2014 at 4:22 PM, Łukasz Górski wrote: > >> > Could you perhaps clarify when exactly do you want this command to be > >> > invoked? Before the reboot or after? If after, perhaps I am mistaken, > >> > but it > >> > doesn't seem to make any sense whatsoever. I suppose you'd need to run > >> > it in > >> > a specific timeframe before the containers are started - how much time it > >> > takes from the moment you get a working shell after the reboot to the > >> > point > >> > when container booting process starts? If you want to run it before the > >> > reboot, then I guess some shell scripting most likely would do to disable > >> > autostart and the re-enable it back again after reboot. > >> > > >> > Pozdrawiam > >> > Łukasz Górski > >> > Biuro Obsługi Klienta LOKIS > >> > www.lokis.info > >> > > >> > --- > >> > Informujemy, że realizujemy projekt „Modernizacja serwerów wewnętrznych i > >> > serwera głównego wraz z konfiguracją”. > >> > Nr wniosku o dofinansowanie: WND-RPPM – 01. – 01.-00 - 363 /08. Projekt > >> > jest > >> > realizowany przy współudziale środków z EFRR oraz budżetu państwa. > >> > Więcej informacji o wniosku i konkursach na stronach www.arp.gda.pl > >> > > >> > > >> > > >> > 2014-08-08 21:21 GMT+02:00 CDR : > >> >> > >> >> Suppose you manage a box with 300 containers, all on autostart=1. One > >> >> day > >> >> you reboot the box but you need to avoid all the contaoners to start. > >> >> There > >> >> should be a command like > >> >> lxc-cancel-autostart. > >> >> Does it make sense? > >> >> > >> >> > >> >> On Friday, August 8, 2014, Harald Dunkel > >> >> wrote: > >> >>> > >> >>> I am not familiar with Ubuntu's setup, but assuming it supports > >> >>> sysv-init I would suggest to omit lxc in a dedicated run level. > >> >>> > >> >>> If your default run level is 2 (specified in /etc/inittab), then > >> >>> you could use update-rc.d to omit lxc in run level 3, e.g. > >> >>> > >> >>> # update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 . > >> >>> > >> >>> This means lxc is started in run levels 2, 4 and 5, and > >> >>> stopped in 0, 1, 3 and 6. > >> >>> > >> >>> If you need to boot without starting the containers, then you > >> >>> can choose run level 3 on the kernel command line at boot time, > >> >>> e.g. > >> >>> linux /boot/vmlinuz root= ... quiet 3 > >> >>> > >> >>> grub2 allows you to modify the kernel command line before booting. > >> >>> Using telinit you can change the run level at run time, e.g. > >> >>> 'telinit 2' to switch to run level 2 (to start your containers). > >> >>> > >> >>> > >> >>> Hope this helps > >> >>> Harri > >> >>> > >> >>> _he__ > >> >>> > >> >>> lxc-users mailing list > >> >>> lxc-users@lists.linuxcontainers.org > >> >>> http://lists.linuxcontainers.org/listinfo/lxc-users > >> >> > >> >> > >> >> ___ > >> >> > >> >> lxc-users mailing list > >> >> lxc-users@lists.linuxcontainers.org > >> >> http://lists.linuxcontainers.org/listinfo/lxc-users > >> > > >> > > >> > > >> > ___ > >>
Re: [lxc-users] How to cancel lxc-autostart
Correct. It is a "cancel fire bullet". I want to ask the developers to create a new command that would do this. On Fri, Aug 8, 2014 at 5:48 PM, Tom Weber wrote: > define a runlevel where the containers are not started or boot in single > user mode and modify the start script. > > that cancel mechanism you ask for is like a 'cancel fired bullet' button > for a gun. > > Tom > > Am Freitag, den 08.08.2014, 16:50 -0400 schrieb CDR: >> After I reboot, the LXC service will start automatically all the >> containers marked for auto-start. I have not found a way to stop that >> mechanism if I absolutely need that the containers to not start. >> Suppose I need to umount the partition to issue an "fsck", etc. How do >> I preempt the automatic behavior? >> It is something like the Iron Dome. Hundreds of containers are on the >> air and will be started, how do you override this behavior? >> >> On Fri, Aug 8, 2014 at 4:22 PM, Łukasz Górski wrote: >> > Could you perhaps clarify when exactly do you want this command to be >> > invoked? Before the reboot or after? If after, perhaps I am mistaken, but >> > it >> > doesn't seem to make any sense whatsoever. I suppose you'd need to run it >> > in >> > a specific timeframe before the containers are started - how much time it >> > takes from the moment you get a working shell after the reboot to the point >> > when container booting process starts? If you want to run it before the >> > reboot, then I guess some shell scripting most likely would do to disable >> > autostart and the re-enable it back again after reboot. >> > >> > Pozdrawiam >> > Łukasz Górski >> > Biuro Obsługi Klienta LOKIS >> > www.lokis.info >> > >> > --- >> > Informujemy, że realizujemy projekt „Modernizacja serwerów wewnętrznych i >> > serwera głównego wraz z konfiguracją”. >> > Nr wniosku o dofinansowanie: WND-RPPM – 01. – 01.-00 - 363 /08. Projekt >> > jest >> > realizowany przy współudziale środków z EFRR oraz budżetu państwa. >> > Więcej informacji o wniosku i konkursach na stronach www.arp.gda.pl >> > >> > >> > >> > 2014-08-08 21:21 GMT+02:00 CDR : >> >> >> >> Suppose you manage a box with 300 containers, all on autostart=1. One day >> >> you reboot the box but you need to avoid all the contaoners to start. >> >> There >> >> should be a command like >> >> lxc-cancel-autostart. >> >> Does it make sense? >> >> >> >> >> >> On Friday, August 8, 2014, Harald Dunkel wrote: >> >>> >> >>> I am not familiar with Ubuntu's setup, but assuming it supports >> >>> sysv-init I would suggest to omit lxc in a dedicated run level. >> >>> >> >>> If your default run level is 2 (specified in /etc/inittab), then >> >>> you could use update-rc.d to omit lxc in run level 3, e.g. >> >>> >> >>> # update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 . >> >>> >> >>> This means lxc is started in run levels 2, 4 and 5, and >> >>> stopped in 0, 1, 3 and 6. >> >>> >> >>> If you need to boot without starting the containers, then you >> >>> can choose run level 3 on the kernel command line at boot time, >> >>> e.g. >> >>> linux /boot/vmlinuz root= ... quiet 3 >> >>> >> >>> grub2 allows you to modify the kernel command line before booting. >> >>> Using telinit you can change the run level at run time, e.g. >> >>> 'telinit 2' to switch to run level 2 (to start your containers). >> >>> >> >>> >> >>> Hope this helps >> >>> Harri >> >>> >> >>> _he__ >> >>> >> >>> lxc-users mailing list >> >>> lxc-users@lists.linuxcontainers.org >> >>> http://lists.linuxcontainers.org/listinfo/lxc-users >> >> >> >> >> >> ___ >> >> >> >> lxc-users mailing list >> >> lxc-users@lists.linuxcontainers.org >> >> http://lists.linuxcontainers.org/listinfo/lxc-users >> > >> > >> > >> > ___ >> > lxc-users mailing list >> > lxc-users@lists.linuxcontainers.org >> > http://lists.linuxcontainers.org/listinfo/lxc-users >> ___ >> lxc-users mailing list >> lxc-users@lists.linuxcontainers.org >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
define a runlevel where the containers are not started or boot in single user mode and modify the start script. that cancel mechanism you ask for is like a 'cancel fired bullet' button for a gun. Tom Am Freitag, den 08.08.2014, 16:50 -0400 schrieb CDR: > After I reboot, the LXC service will start automatically all the > containers marked for auto-start. I have not found a way to stop that > mechanism if I absolutely need that the containers to not start. > Suppose I need to umount the partition to issue an "fsck", etc. How do > I preempt the automatic behavior? > It is something like the Iron Dome. Hundreds of containers are on the > air and will be started, how do you override this behavior? > > On Fri, Aug 8, 2014 at 4:22 PM, Łukasz Górski wrote: > > Could you perhaps clarify when exactly do you want this command to be > > invoked? Before the reboot or after? If after, perhaps I am mistaken, but it > > doesn't seem to make any sense whatsoever. I suppose you'd need to run it in > > a specific timeframe before the containers are started - how much time it > > takes from the moment you get a working shell after the reboot to the point > > when container booting process starts? If you want to run it before the > > reboot, then I guess some shell scripting most likely would do to disable > > autostart and the re-enable it back again after reboot. > > > > Pozdrawiam > > Łukasz Górski > > Biuro Obsługi Klienta LOKIS > > www.lokis.info > > > > --- > > Informujemy, że realizujemy projekt „Modernizacja serwerów wewnętrznych i > > serwera głównego wraz z konfiguracją”. > > Nr wniosku o dofinansowanie: WND-RPPM – 01. – 01.-00 - 363 /08. Projekt jest > > realizowany przy współudziale środków z EFRR oraz budżetu państwa. > > Więcej informacji o wniosku i konkursach na stronach www.arp.gda.pl > > > > > > > > 2014-08-08 21:21 GMT+02:00 CDR : > >> > >> Suppose you manage a box with 300 containers, all on autostart=1. One day > >> you reboot the box but you need to avoid all the contaoners to start. There > >> should be a command like > >> lxc-cancel-autostart. > >> Does it make sense? > >> > >> > >> On Friday, August 8, 2014, Harald Dunkel wrote: > >>> > >>> I am not familiar with Ubuntu's setup, but assuming it supports > >>> sysv-init I would suggest to omit lxc in a dedicated run level. > >>> > >>> If your default run level is 2 (specified in /etc/inittab), then > >>> you could use update-rc.d to omit lxc in run level 3, e.g. > >>> > >>> # update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 . > >>> > >>> This means lxc is started in run levels 2, 4 and 5, and > >>> stopped in 0, 1, 3 and 6. > >>> > >>> If you need to boot without starting the containers, then you > >>> can choose run level 3 on the kernel command line at boot time, > >>> e.g. > >>> linux /boot/vmlinuz root= ... quiet 3 > >>> > >>> grub2 allows you to modify the kernel command line before booting. > >>> Using telinit you can change the run level at run time, e.g. > >>> 'telinit 2' to switch to run level 2 (to start your containers). > >>> > >>> > >>> Hope this helps > >>> Harri > >>> > >>> _he__ > >>> > >>> lxc-users mailing list > >>> lxc-users@lists.linuxcontainers.org > >>> http://lists.linuxcontainers.org/listinfo/lxc-users > >> > >> > >> ___ > >> > >> lxc-users mailing list > >> lxc-users@lists.linuxcontainers.org > >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > > > > > > ___ > > lxc-users mailing list > > lxc-users@lists.linuxcontainers.org > > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
On Fri, 2014-08-08 at 16:50 -0400, CDR wrote: > After I reboot, the LXC service will start automatically all the > containers marked for auto-start. I have not found a way to stop that > mechanism if I absolutely need that the containers to not start. > Suppose I need to umount the partition to issue an "fsck", etc. How do > I preempt the automatic behavior? > It is something like the Iron Dome. Hundreds of containers are on the > air and will be started, how do you override this behavior? I would suggest putting them in a different group and deferring their startup until you're sure you don't need to interrupt the process if that's your problem. You could easily script that. Just run a bootup timer out of cron and run "lxc-autostart -g "defer-boot-group". Otherwise, you're going to be piled with race conditions. Regards, Mike > On Fri, Aug 8, 2014 at 4:22 PM, Łukasz Górski wrote: > > Could you perhaps clarify when exactly do you want this command to be > > invoked? Before the reboot or after? If after, perhaps I am mistaken, but it > > doesn't seem to make any sense whatsoever. I suppose you'd need to run it in > > a specific timeframe before the containers are started - how much time it > > takes from the moment you get a working shell after the reboot to the point > > when container booting process starts? If you want to run it before the > > reboot, then I guess some shell scripting most likely would do to disable > > autostart and the re-enable it back again after reboot. > > > > Pozdrawiam > > Łukasz Górski > > Biuro Obsługi Klienta LOKIS > > www.lokis.info > > > > --- > > Informujemy, że realizujemy projekt „Modernizacja serwerów wewnętrznych i > > serwera głównego wraz z konfiguracją”. > > Nr wniosku o dofinansowanie: WND-RPPM – 01. – 01.-00 - 363 /08. Projekt jest > > realizowany przy współudziale środków z EFRR oraz budżetu państwa. > > Więcej informacji o wniosku i konkursach na stronach www.arp.gda.pl > > > > > > > > 2014-08-08 21:21 GMT+02:00 CDR : > >> > >> Suppose you manage a box with 300 containers, all on autostart=1. One day > >> you reboot the box but you need to avoid all the contaoners to start. There > >> should be a command like > >> lxc-cancel-autostart. > >> Does it make sense? > >> > >> > >> On Friday, August 8, 2014, Harald Dunkel wrote: > >>> > >>> I am not familiar with Ubuntu's setup, but assuming it supports > >>> sysv-init I would suggest to omit lxc in a dedicated run level. > >>> > >>> If your default run level is 2 (specified in /etc/inittab), then > >>> you could use update-rc.d to omit lxc in run level 3, e.g. > >>> > >>> # update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 . > >>> > >>> This means lxc is started in run levels 2, 4 and 5, and > >>> stopped in 0, 1, 3 and 6. > >>> > >>> If you need to boot without starting the containers, then you > >>> can choose run level 3 on the kernel command line at boot time, > >>> e.g. > >>> linux /boot/vmlinuz root= ... quiet 3 > >>> > >>> grub2 allows you to modify the kernel command line before booting. > >>> Using telinit you can change the run level at run time, e.g. > >>> 'telinit 2' to switch to run level 2 (to start your containers). > >>> > >>> > >>> Hope this helps > >>> Harri > >>> > >>> _he__ > >>> > >>> lxc-users mailing list > >>> lxc-users@lists.linuxcontainers.org > >>> http://lists.linuxcontainers.org/listinfo/lxc-users > >> > >> > >> ___ > >> > >> lxc-users mailing list > >> lxc-users@lists.linuxcontainers.org > >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > > > > > > ___ > > lxc-users mailing list > > lxc-users@lists.linuxcontainers.org > > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > -- Michael H. Warfield (AI4NB) | (770) 978-7061 | m...@wittsend.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it! signature.asc Description: This is a digitally signed message part ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
Use your init system. Quoting CDR (vene...@gmail.com): > After I reboot, the LXC service will start automatically all the > containers marked for auto-start. I have not found a way to stop that > mechanism if I absolutely need that the containers to not start. > Suppose I need to umount the partition to issue an "fsck", etc. How do > I preempt the automatic behavior? > It is something like the Iron Dome. Hundreds of containers are on the > air and will be started, how do you override this behavior? > > On Fri, Aug 8, 2014 at 4:22 PM, Łukasz Górski wrote: > > Could you perhaps clarify when exactly do you want this command to be > > invoked? Before the reboot or after? If after, perhaps I am mistaken, but it > > doesn't seem to make any sense whatsoever. I suppose you'd need to run it in > > a specific timeframe before the containers are started - how much time it > > takes from the moment you get a working shell after the reboot to the point > > when container booting process starts? If you want to run it before the > > reboot, then I guess some shell scripting most likely would do to disable > > autostart and the re-enable it back again after reboot. > > > > Pozdrawiam > > Łukasz Górski > > Biuro Obsługi Klienta LOKIS > > www.lokis.info > > > > --- > > Informujemy, że realizujemy projekt „Modernizacja serwerów wewnętrznych i > > serwera głównego wraz z konfiguracją”. > > Nr wniosku o dofinansowanie: WND-RPPM – 01. – 01.-00 - 363 /08. Projekt jest > > realizowany przy współudziale środków z EFRR oraz budżetu państwa. > > Więcej informacji o wniosku i konkursach na stronach www.arp.gda.pl > > > > > > > > 2014-08-08 21:21 GMT+02:00 CDR : > >> > >> Suppose you manage a box with 300 containers, all on autostart=1. One day > >> you reboot the box but you need to avoid all the contaoners to start. There > >> should be a command like > >> lxc-cancel-autostart. > >> Does it make sense? > >> > >> > >> On Friday, August 8, 2014, Harald Dunkel wrote: > >>> > >>> I am not familiar with Ubuntu's setup, but assuming it supports > >>> sysv-init I would suggest to omit lxc in a dedicated run level. > >>> > >>> If your default run level is 2 (specified in /etc/inittab), then > >>> you could use update-rc.d to omit lxc in run level 3, e.g. > >>> > >>> # update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 . > >>> > >>> This means lxc is started in run levels 2, 4 and 5, and > >>> stopped in 0, 1, 3 and 6. > >>> > >>> If you need to boot without starting the containers, then you > >>> can choose run level 3 on the kernel command line at boot time, > >>> e.g. > >>> linux /boot/vmlinuz root= ... quiet 3 > >>> > >>> grub2 allows you to modify the kernel command line before booting. > >>> Using telinit you can change the run level at run time, e.g. > >>> 'telinit 2' to switch to run level 2 (to start your containers). > >>> > >>> > >>> Hope this helps > >>> Harri > >>> > >>> _he__ > >>> > >>> lxc-users mailing list > >>> lxc-users@lists.linuxcontainers.org > >>> http://lists.linuxcontainers.org/listinfo/lxc-users > >> > >> > >> ___ > >> > >> lxc-users mailing list > >> lxc-users@lists.linuxcontainers.org > >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > > > > > > ___ > > lxc-users mailing list > > lxc-users@lists.linuxcontainers.org > > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
After I reboot, the LXC service will start automatically all the containers marked for auto-start. I have not found a way to stop that mechanism if I absolutely need that the containers to not start. Suppose I need to umount the partition to issue an "fsck", etc. How do I preempt the automatic behavior? It is something like the Iron Dome. Hundreds of containers are on the air and will be started, how do you override this behavior? On Fri, Aug 8, 2014 at 4:22 PM, Łukasz Górski wrote: > Could you perhaps clarify when exactly do you want this command to be > invoked? Before the reboot or after? If after, perhaps I am mistaken, but it > doesn't seem to make any sense whatsoever. I suppose you'd need to run it in > a specific timeframe before the containers are started - how much time it > takes from the moment you get a working shell after the reboot to the point > when container booting process starts? If you want to run it before the > reboot, then I guess some shell scripting most likely would do to disable > autostart and the re-enable it back again after reboot. > > Pozdrawiam > Łukasz Górski > Biuro Obsługi Klienta LOKIS > www.lokis.info > > --- > Informujemy, że realizujemy projekt „Modernizacja serwerów wewnętrznych i > serwera głównego wraz z konfiguracją”. > Nr wniosku o dofinansowanie: WND-RPPM – 01. – 01.-00 - 363 /08. Projekt jest > realizowany przy współudziale środków z EFRR oraz budżetu państwa. > Więcej informacji o wniosku i konkursach na stronach www.arp.gda.pl > > > > 2014-08-08 21:21 GMT+02:00 CDR : >> >> Suppose you manage a box with 300 containers, all on autostart=1. One day >> you reboot the box but you need to avoid all the contaoners to start. There >> should be a command like >> lxc-cancel-autostart. >> Does it make sense? >> >> >> On Friday, August 8, 2014, Harald Dunkel wrote: >>> >>> I am not familiar with Ubuntu's setup, but assuming it supports >>> sysv-init I would suggest to omit lxc in a dedicated run level. >>> >>> If your default run level is 2 (specified in /etc/inittab), then >>> you could use update-rc.d to omit lxc in run level 3, e.g. >>> >>> # update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 . >>> >>> This means lxc is started in run levels 2, 4 and 5, and >>> stopped in 0, 1, 3 and 6. >>> >>> If you need to boot without starting the containers, then you >>> can choose run level 3 on the kernel command line at boot time, >>> e.g. >>> linux /boot/vmlinuz root= ... quiet 3 >>> >>> grub2 allows you to modify the kernel command line before booting. >>> Using telinit you can change the run level at run time, e.g. >>> 'telinit 2' to switch to run level 2 (to start your containers). >>> >>> >>> Hope this helps >>> Harri >>> >>> _he__ >>> >>> lxc-users mailing list >>> lxc-users@lists.linuxcontainers.org >>> http://lists.linuxcontainers.org/listinfo/lxc-users >> >> >> ___ >> >> lxc-users mailing list >> lxc-users@lists.linuxcontainers.org >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
Could you perhaps clarify when exactly do you want this command to be invoked? Before the reboot or after? If after, perhaps I am mistaken, but it doesn't seem to make any sense whatsoever. I suppose you'd need to run it in a specific timeframe before the containers are started - how much time it takes from the moment you get a working shell after the reboot to the point when container booting process starts? If you want to run it before the reboot, then I guess some shell scripting most likely would do to disable autostart and the re-enable it back again after reboot. Pozdrawiam Łukasz Górski Biuro Obsługi Klienta LOKIS www.lokis.info --- Informujemy, że realizujemy projekt „Modernizacja serwerów wewnętrznych i serwera głównego wraz z konfiguracją”. Nr wniosku o dofinansowanie: WND-RPPM – 01. – 01.-00 - 363 /08. Projekt jest realizowany przy współudziale środków z EFRR oraz budżetu państwa. Więcej informacji o wniosku i konkursach na stronach www.arp.gda.pl 2014-08-08 21:21 GMT+02:00 CDR : > Suppose you manage a box with 300 containers, all on autostart=1. One day > you reboot the box but you need to avoid all the contaoners to start. There > should be a command like > lxc-cancel-autostart. > Does it make sense? > > > On Friday, August 8, 2014, Harald Dunkel wrote: > >> I am not familiar with Ubuntu's setup, but assuming it supports >> sysv-init I would suggest to omit lxc in a dedicated run level. >> >> If your default run level is 2 (specified in /etc/inittab), then >> you could use update-rc.d to omit lxc in run level 3, e.g. >> >> # update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 . >> >> This means lxc is started in run levels 2, 4 and 5, and >> stopped in 0, 1, 3 and 6. >> >> If you need to boot without starting the containers, then you >> can choose run level 3 on the kernel command line at boot time, >> e.g. >> linux /boot/vmlinuz root= ... quiet 3 >> >> grub2 allows you to modify the kernel command line before booting. >> Using telinit you can change the run level at run time, e.g. >> 'telinit 2' to switch to run level 2 (to start your containers). >> >> >> Hope this helps >> Harri >> >> _he__ >> >> lxc-users mailing list >> lxc-users@lists.linuxcontainers.org >> http://lists.linuxcontainers.org/listinfo/lxc-users >> > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
Suppose you manage a box with 300 containers, all on autostart=1. One day you reboot the box but you need to avoid all the contaoners to start. There should be a command like lxc-cancel-autostart. Does it make sense? On Friday, August 8, 2014, Harald Dunkel wrote: > I am not familiar with Ubuntu's setup, but assuming it supports > sysv-init I would suggest to omit lxc in a dedicated run level. > > If your default run level is 2 (specified in /etc/inittab), then > you could use update-rc.d to omit lxc in run level 3, e.g. > > # update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 . > > This means lxc is started in run levels 2, 4 and 5, and > stopped in 0, 1, 3 and 6. > > If you need to boot without starting the containers, then you > can choose run level 3 on the kernel command line at boot time, > e.g. > linux /boot/vmlinuz root= ... quiet 3 > > grub2 allows you to modify the kernel command line before booting. > Using telinit you can change the run level at run time, e.g. > 'telinit 2' to switch to run level 2 (to start your containers). > > > Hope this helps > Harri > > _he__ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] How to cancel lxc-autostart
I am not familiar with Ubuntu's setup, but assuming it supports sysv-init I would suggest to omit lxc in a dedicated run level. If your default run level is 2 (specified in /etc/inittab), then you could use update-rc.d to omit lxc in run level 3, e.g. # update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 . This means lxc is started in run levels 2, 4 and 5, and stopped in 0, 1, 3 and 6. If you need to boot without starting the containers, then you can choose run level 3 on the kernel command line at boot time, e.g. linux /boot/vmlinuz root= ... quiet 3 grub2 allows you to modify the kernel command line before booting. Using telinit you can change the run level at run time, e.g. 'telinit 2' to switch to run level 2 (to start your containers). Hope this helps Harri ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] How to cancel lxc-autostart
Dear Friends I am using Ubuntu 14.04 and LXC latest. When the machine boots I would like to cancel lxc-autostart, since I have a lot of containers and I need to fix something first. Is there a way? If not, maybe we may add a new command for that. Also, I still cannot install lxc-top, to see what container is eating at my resources. Philip ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
