It appears the lag of a few seconds is enough to prevent other network-
required services from starting. I have tried with openvpn and
dhcp3-server. So I need to resort to the same rc.local [1] I had when
the bridge wasn't coming up at all pre-Lucid. I have tested this on
Maverick only.
[1]:
i
On Mon, Dec 20, 2010 at 07:46:41PM -, Peter Matulis wrote:
> I will try it again soon on my similarly plagued Karmic machine.
Oh, this is definitely broken on karmic. The fixes for upstartification of
bridge-utils were only ever included in lucid, they weren't backported to
karmic.
--
Steve
Weird. Either there was a recent update or there was a wicked delay for
the bridge to come up because it's working now (with a delay of around 5
seconds). I will try it again soon on my similarly plagued Karmic
machine.
--
You received this bug notification because you are a member of Ubuntu
Se
Please boot with '--verbose' added to the kernel boot options and attach
the resulting /var/log/syslog, so we can trace the resulting upstart
events.
** Changed in: bridge-utils (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Ser
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: bridge-utils
On a fresh (vmbuilder) install of Maverick (server 64-bit) I cannot get
a vanilla bridge to come up upon boot using the standard configuration
method (via /etc/network/interfac
