This bug is ridiculous. Won't Fix? And no kidding?!?
I don't care if it is related to retries or a timeout. But if it's decided
that in some environment it would be useful for reliability sake to have such
timeout, it would be great to improve this feature with some option, like:
- a place
On Thu, Feb 23, 2012 at 09:20:47PM -, goto wrote:
This bug is ridiculous. Won't Fix? And no kidding?!?
Yes, we are not going to fix the system in a way that causes the user's
configured and installed services to arbitrarily fail to start correctly on
boot because of a network startup delay.
Well, it would be good to confirm whether this is the case currently
or not.
Hi
Finally had time to test this again.
I deleted my Wifi configuration from my laptop. The Waiting for network
connection... text doesn't come back anymore.
I also had one more laptop that wasn't yet updated to
Steve, what do you mean invalid? What do you mean with unreliable boot
sequence?
I have a laptop. I take it onto a business trip. I want to work on the
airplane. There is no internet connection within miles. That (K)Ubuntu
wants to wait for several minutes until it accepts the fact that there
is
Steve says that the delay occurs [only] if you have misconfigured
/etc/network/interfaces. So if you want a faster boot, fix your network
config - -.
Your clause is wrong if you we assume that /etc/network/interfaces are
configured correctly in the fresh installation. The delay occurs also
with a
Please attach the /etc/network/interfaces from the affected system. If
there are delays with the stock file as shipped in any of our releases,
that's definitely something that we need to clean up; but that's not
something that anyone ran into during development, and not what the
original bug
@Steve I will du it in the middle of February as I am back in the
university then from holiday. Yes, the delays are with the stock file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886414
Title:
FWIW, here's my
$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
Note that:
- this is not from fresh install but the system was upgraded a few
times from previous Kubuntu versions, I don't know how much the file has
lived on since then.
- I'm actually not sure my system suffers
On Fri, Jan 06, 2012 at 09:00:03PM -, Henrik Ingo wrote:
Steve, what do you mean invalid?
An interfaces file that lists an interface as 'auto' which will not be
available at boot time.
What do you mean with unreliable boot sequence?
Not waiting for the configured network interfaces to
Just because a system is a desktop system doesn't mean that it's ok to
have an unreliable boot sequence. You will only see delays in boot if
you have misconfigured /etc/network/interfaces. So if you want a faster
boot, fix your network config...
** Changed in: upstart
Status: Incomplete
Ok, and there's a way to configure how many retries are done?
Perhaps, in my network i've found that reliability is greatly improved
by setting up retries to be done for 3 minutes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What retries are you talking about? The system doesn't retry anything
related to networking, generally, except for dhcp. Most of this time is
just spent waiting for the devices to be configured - in the case of a
broken configuration in /etc/network/interfaces, this is waiting for
devices that
Steve: I'm sorry i was thinking with the contextual information from the
link in the bug-report which refers to the dhcp retries.
Indeed, in my case is due to dhcp, perhaps i'm missing something, but
that happened when not using network-manager and having configured dhcp
for some of the networks
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886414
Title:
No
This bug was marked as a duplicate of #856810 but it is not. This bug is
about a laptop/desktop user having to wait at boot time. The other is
about system failing to start at all.
** This bug is no longer a duplicate of bug 856810
Boot hangs at Booting system without full network
Henrik is right. It's not only the server version of ubuntu. It affects
also normal Laptop users and it's realy anoying to wait every boot for
90 secounds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: upstart (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886414
Title:
No 2 Minute pause at login for Server Boot in Ubuntu Desktop
To manage
This is annoying when I want to configure network interfaces via
interfaces(5). Network Manager can do just a little simple
configuration. Why should this even be call by the developer a feature?
** Package changed: xorg (Ubuntu) = ubuntu
** Changed in: ubuntu
Status: Invalid = Opinion
*** This bug is a duplicate of bug 856810 ***
https://bugs.launchpad.net/bugs/856810
** This bug has been marked a duplicate of bug 856810
Boot hangs at Booting system without full network configuration...
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886414
Title:
No 2 Minute pause at login for Server Boot in Ubuntu Desktop
To manage
The bug is a desing bug: separate Ubuntu Server completely from Ubuntu
Desktop. It is not in Xorg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886414
Title:
No 2 Minute pause at login for Server
21 matches
Mail list logo
