<div dir="ltr">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.<br>
</div><div class="gmail_extra"><br clear="all"><div>Pozdrawiam<br>Łukasz Górski<br>Biuro Obsługi Klienta LOKIS<br><a href="http://www.lokis.info" target="_blank">www.lokis.info</a><br><pre>---
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 <a href="http://www.arp.gda.pl" target="_blank">www.arp.gda.pl</a></pre></div>
<br><br><div class="gmail_quote">2014-08-08 21:21 GMT+02:00 CDR <span dir="ltr"><<a href="mailto:venefax@gmail.com" target="_blank">venefax@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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<div>lxc-cancel-autostart.</div><div>Does it make sense?</div>
<div><div class=""><br><br>On Friday, August 8, 2014, Harald Dunkel <<a href="mailto:harald.dunkel@aixigo.de" target="_blank">harald.dunkel@aixigo.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
I am not familiar with Ubuntu's setup, but assuming it supports<br>
sysv-init I would suggest to omit lxc in a dedicated run level.<br>
<br>
If your default run level is 2 (specified in /etc/inittab), then<br>
you could use update-rc.d to omit lxc in run level 3, e.g.<br>
<br>
# update-rc.d lxc start 20 2 4 5 . stop 20 0 1 3 6 .<br>
<br>
This means lxc is started in run levels 2, 4 and 5, and<br>
stopped in 0, 1, 3 and 6.<br>
<br>
If you need to boot without starting the containers, then you<br>
can choose run level 3 on the kernel command line at boot time,<br>
e.g.<br>
linux /boot/vmlinuz root= ... quiet 3<br>
<br>
grub2 allows you to modify the kernel command line before booting.<br>
Using telinit you can change the run level at run time, e.g.<br>
'telinit 2' to switch to run level 2 (to start your containers).<br>
<br>
<br>
Hope this helps<br>
Harri<br>
<br></div>
_____________________________________________he__<div class=""><br>
lxc-users mailing list<br>
<a>lxc-users@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a></div></blockquote></div>
<br>_______________________________________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br></blockquote></div><br></div>