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. Ev
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
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
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
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
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 cont
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 thei
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_ st
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 grou
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 mech
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 st
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 iss
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 partit
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 beha
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 t
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 Ubunt
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 . st
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 co
18 matches
Mail list logo
