hi All,
Regarding the bug #1087765 is there a way in Ubuntu to specify the starting
order of containers?
I this this code in /etc/init/lxc.conf:
for f in /etc/lxc/auto/*; do
c="$(basename $f .conf)"
lxc-info -n $c 2>/dev/null | grep state | grep -q "RUNNING" ||
lxc-start -n $c -f $f -d
done
Why are they started with '-f <config file>'?
Why not just 'lxc-start -n $c -d'
I think it would be simple using a config file with the order of the specific
or with all the
container names.
Something like this:
/etc/lxc/order.conf:
dnsserver
ldapserver
puppet
If exists, these containers would be started started first.
Maybe specifying delay would also be useful?
Eg:
/etc/lxc/order.conf:
dnsserver:15
ldapserver:30
puppet:15
Where numbers mean secundums, eg. dns server receives 15 secundums to startup
properly.
Essential services would be working before anything else and users would be
happy:)
What do you think about that?
Thanks,
tamas
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
