http://bugzilla.openvz.org/show_bug.cgi?id=1300 says that this is
implemented in vzctl = 3.0.24 so marking this Fix Released
** Changed in: vzctl (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Should be fixed in 3.0.24, which hopefully makes it into Ubuntu Maverick
still (bug 628965).
** Changed in: openvz-tools
Importance: Unknown = Undecided
** Changed in: openvz-tools
Status: Confirmed = New
** Changed in: openvz-tools
Remote watch: OpenVZ Bugzilla #1300 = None
** Bug
Hello Daniel,
I think you're right... follows a revised patch which does not brake the
expected behavior of the ONBOOT parameter. Human-friendly put:
- first use the (valid/ONBOOT) VEIDs in the BOOT_ORDER file
- then add the ONBOOT VEIDs that do not appear in the BOOT_ORDER file
I will also
** Bug watch added: OpenVZ Bugzilla #1300
http://bugzilla.openvz.org/show_bug.cgi?id=1300
** Also affects: openvz-tools via
http://bugzilla.openvz.org/show_bug.cgi?id=1300
Importance: Unknown
Status: Unknown
--
WISH: allow to specify VEs boot order for /etc/init.d/vz
** Changed in: openvz-tools
Status: Unknown = Confirmed
--
WISH: allow to specify VEs boot order for /etc/init.d/vz
https://bugs.launchpad.net/bugs/394885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: Allow to specify VEs boot order in OpenVZ startup script
http://launchpadlibrarian.net/28637786/vz.patch
--
WISH: allow to specify VEs boot order for /etc/init.d/vz
https://bugs.launchpad.net/bugs/394885
You received this bug notification because you are a member of
Thank you attacking this, I think it's a really useful wish.
However, the implementation should make sure, that any ONBOOT containers get
started.
I propose to use the BOOT file, but append any containers not listed in there
to the generated list.
What do you think?
Anyway, this is a nice
