Even if network is fully configured upstart waits for network configuration up to three minutes
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Even if network is fully configured, upstart waits up to three minutes for network configuration. In between, some services are started (sshd), while others are not (autofs). This leads to situations, where users may login, not connected to there home, but to "/".
In tune this may lead to unexpected security breaches.
upstart shall have an other way detecting networking is up as it does now, depending on NetworkManager purely. Servers do not need NetworkManager: they have, in almost all cases statically assigned addresses!
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: upstart 1.3-0ubuntu12
Uname: Linux 3.2.16 x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sun May 6 11:45:33 2012
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
| Thomas Schweikle (tps) wrote | #1 |
| security vulnerability: | yes → no |
| visibility: | private → public |
| Gary Houston (ghouston) wrote | #2 |
| Gary Houston (ghouston) wrote | #3 |
I just had to edit /etc/init/
My setup is a bit unusual, but not too bizarre. I have a router with a single ethernet connection which is connected to my main computer. I have a second network card which connects it to a second computer (used by my partner). I have a script that enables NAT forwarding to the 2nd computer (which itself isn't very user-friendly to configure, but that's a different story) but it doesn't play well with network-manager so I've uninstalled that latter and configured the network manually in /etc/network/
Now I find that everthing works fine if I switch on both computers together, which is the usual case. However if I switch on mine only, it hangs in failsafe.conf. Editing failsafe.conf seemed like the best solution, but it's not very elegant.