| Eruantalon | My problem is that my boot time goes up by 120 seconds(more or less) when no cable is present(laptop) | 12:24 |
|---|---|---|
| mbiebl | Eruantalon: If you need a more lightweight solution than NetworkManager, use ifplugd | 12:24 |
| wasabi | And what causes that to happen? | 12:24 |
| Eruantalon | wasabi, well bootchart tells me it hangs on dhclient-script which is called by ifup.. I gather that means that it is stuck waiting for network configuring data that never comes | 12:26 |
| Eruantalon | because of lack of link to the outside world | 12:26 |
| wasabi | Uh huh. So don't bring up network automatically using Debian tools. | 12:26 |
| wasabi | Remove 'auto' from /etc/network/interfaces | 12:26 |
| mbiebl | But only for eth*. You still want your loopback device setup ;-) | 12:27 |
| wasabi | Yes yes | 12:28 |
| Eruantalon | wasabi, And put what in its place (I gather that is the same thing as disabling roaming mode in networksettings? | 12:29 |
| wasabi | Use network manager. | 12:29 |
| wasabi | Completely bypasses that. | 12:29 |
| Eruantalon | OK. | 12:29 |
| Eruantalon | But is there a way to make sure that it still happens upon entering gnome? | 12:30 |
| Eruantalon | I'd like the roaming features, works great, just not while booting. | 12:30 |
| wasabi | Hmm? | 12:30 |
| wasabi | That's what network manager is for. | 12:30 |
| Eruantalon | Ok, Then tell me should roaming be on or off? | 12:31 |
| mbiebl | Eruantalon: What do you mean by "roaming mode", switching automatically between available wireless networks? | 12:32 |
| Eruantalon | mbiebl, yes. But it is not my expression it says that in network settings | 12:32 |
| wasabi | I don't even know what screen you are refering to. | 12:32 |
| mbiebl | Eruantalon: If you are using wireless, network-manager is indeed the best choice for you. | 12:33 |
| Eruantalon | Ok just to make sure that we are talking about the same thing... What network manager are you talking about? | 12:33 |
| mbiebl | Just make sure, you comment all all eth* entries in /etc/network/interfaces | 12:33 |
| wasabi | apt-get install network-manager-gnome | 12:34 |
| wasabi | The only one of all of the solutions named "network manager" | 12:34 |
| Eruantalon | and what command opens it? | 12:34 |
| wasabi | It adds itself to your session. Install it, log out, then back in. | 12:34 |
| Eruantalon | mbiebl, I am using both wireless and wired( because sometimes wireles is to slow) | 12:35 |
| wasabi | Or run "nm-applet" | 12:35 |
| mbiebl | Better: "nm-applet --sm-disable" | 12:35 |
| wasabi | What's sm-disable do? | 12:35 |
| Eruantalon | wasabi, Ok, That is the same thing as what i've already got | 12:35 |
| mbiebl | Otherwise you will have two nm-applet instances nextt time you log in. | 12:35 |
| wasabi | Eruantalon: Okay, and what's wrong with it? | 12:36 |
| mbiebl | Eruantalon: Have you read /usr/share/doc/network-manager/README.Debian? | 12:36 |
| Eruantalon | Well Nothing. It is the startup scritpt during boot that wants to start networking when there is no cable which is a problem | 12:36 |
| wasabi | Nope, it's not. | 12:36 |
| wasabi | It does not block boot. | 12:37 |
| wasabi | Again, Debian network infrastructure does that. | 12:37 |
| wasabi | Again, comment out the auto lines for eth* in /etc/network/interfaces | 12:37 |
| Eruantalon | wasabi, And put nothing instead? | 12:37 |
| mbiebl | yes. | 12:37 |
| wasabi | I'm about done with this. | 12:37 |
| Eruantalon | And that will make sure nothing network related is started until gnome is? | 12:38 |
| wasabi | No. It will not make sure of that. | 12:38 |
| Eruantalon | Thanks a bunch anyway | 12:38 |
| wasabi | It will not use Debian's network infrastructure to start dhclient and block on it. That is all it will do. | 12:38 |
| wasabi | If you have other pieces of software which block on the network, you'll need to fix those. | 12:38 |
| wasabi | Such as for instance mounting network file systems in fstab. | 12:38 |
| wasabi | Also, as soon as the network manager daemon is started, it goes off and starts dhclient, in the background. | 12:38 |
| Eruantalon | Well I've commented out the two auto's and I guess I will have to restart to see what happens. Thanks. | 12:40 |
| wasabi | Do not comment out auto lo | 12:40 |
| wasabi | As mbiebl said earlier. | 12:40 |
| Eruantalon | I haven't :-) | 12:40 |
| mbiebl | Eruantalon: please pastebin your /etc/network/interfaces | 12:41 |
| Eruantalon | ok two seconds | 12:41 |
| Eruantalon | http://paste.ubuntu-nl.org/32977/ | 12:42 |
| Eruantalon | Ok? | 12:43 |
| wasabi | You have the wireless interfaces set to auto also. | 12:43 |
| wasabi | You'll want to disable them too. | 12:43 |
| wasabi | The idea is whatever you set to auto and dhcp results in dhclient being started at boot, and waiting. | 12:43 |
| Eruantalon | everything but lo ? | 12:43 |
| wasabi | Correct. | 12:44 |
| Eruantalon | thanks | 12:44 |
| === tck [n=tck@213-202-161-88.bas503.dsl.esat.net] has joined #upstart | ||
| mbiebl | Eruantalon: you can remove everything besides | 12:44 |
| mbiebl | auto lo | 12:44 |
| mbiebl | iface lo inet loopback | 12:44 |
| Eruantalon | without screwing anything up? | 12:45 |
| mbiebl | If you have NM, you are fine. | 12:45 |
| mbiebl | But this is getting mighty OT now. | 12:46 |
| Eruantalon | Well I don't know if I will be going back so I'll leave it be. Never know when I want to have network during again? | 12:46 |
| Eruantalon | mbiebl, Sorry, But I thought it was something upstart would be able to do simply- | 12:46 |
| === Eruantalon [n=hans@5634185c.rev.stofanet.dk] has joined #upstart | ||
| Eruantalon | Thanks. That did the trick | 12:49 |
| mbiebl | Eruantalon: the main idea behind upstart is, that it is event based. | 12:50 |
| Eruantalon | yep | 12:50 |
| mbiebl | You still need sources, which generate these events. | 12:50 |
| mbiebl | NM could be such a source for network events. | 12:51 |
| Eruantalon | mbiebl, I just thought that upstart was the underlying thing that drove network manager | 12:51 |
| Eruantalon | Do you know then where I should go to file a bug about this problem then. I gather it is the startupscripts in ubuntu and not a bug in upstart itself | 12:52 |
| mbiebl | Well, upstart is mainly a event queue and dispatcher. | 12:52 |
| mbiebl | It has no knowledge about network and stuff. | 12:52 |
| mbiebl | That's what I meant, when I said these kind of events have to be feed into upstart from external sources. | 12:53 |
| === tck [n=tck@213-202-161-88.bas503.dsl.esat.net] has joined #upstart | ||
| Eruantalon | Hmm I gotta reboot to check something. It seems that network manager lost any information about my wireless card... | 12:54 |
| === btm [n=btm@gir.seattlewireless.net] has joined #upstart | ||
| === btm [n=btm@gir.seattlewireless.net] has joined #upstart | ||
| === juergbi [n=juerg@80-219-19-183.dclient.hispeed.ch] has joined #upstart | ||
| === sadleder [n=sadleder@p50812650.dip0.t-ipconnect.de] has joined #upstart | ||
| === sadleder [n=sadleder@p50812650.dip0.t-ipconnect.de] has left #upstart [] | ||
| === Md [i=md@freenode/staff/md] has joined #upstart | ||
| === Keybuk [i=scott@nat/canonical/x-a1815f81a5b95fe2] has joined #upstart | ||
| AlexExtreme | Keybuk, do you know if the ubuntu server guys are planning to have the whole of EBox packaged in gutsy? i tried out tribe3 the other day, and did an aptitude update/upgrade, but still only a few of the ebox modules are there | 12:04 |
| === Amaranth_ [n=travis@ubuntu/member/Amaranth] has joined #upstart | ||
| === mbiebl [n=michael@e180070127.adsl.alicedsl.de] has joined #upstart | ||
| Keybuk | AlexExtreme: no idea, sorry | 01:10 |
| Keybuk | I would imagine so | 01:10 |
| AlexExtreme | ok, thanks | 01:11 |
| AlexExtreme | also, one more Q: do you plan to get native upstart jobs into gutsy? | 01:11 |
| Keybuk | no | 01:11 |
| === tck [n=tck@213-202-142-118.bas502.dsl.esat.net] has joined #upstart | ||
| === sadleder [n=sadleder@p50812650.dip0.t-ipconnect.de] has joined #upstart | ||
| === sadleder [n=sadleder@p50812650.dip0.t-ipconnect.de] has left #upstart [] | ||
| === tale_ [n=tale@207.235.54.1] has joined #upstart | ||
| === jonibo [n=jonas@ua-83-227-144-18.cust.bredbandsbolaget.se] has joined #upstart | ||
| === rawler [n=ulrik@c-e54fe155.98-2-64736c13.cust.bredbandsbolaget.se] has joined #upstart | ||
| === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart | ||
| === tck_ [n=tck@A-105-125.cust.iol.ie] has joined #upstart | ||
| === Starting logfile irclogs/upstart.log | ||
| === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #upstart | ||
| === Topic for #upstart: Upstart 0.3.8 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/wiki/UpstartOnGentoo | http://people.ubuntu.com/~fabbione/irclogs/ | ||
| === Topic (#upstart): set by AlexExtreme at Tue Jul 31 10:13:07 2007 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!