[12:24] My problem is that my boot time goes up by 120 seconds(more or less) when no cable is present(laptop) [12:24] Eruantalon: If you need a more lightweight solution than NetworkManager, use ifplugd [12:24] And what causes that to happen? [12:26] 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] because of lack of link to the outside world [12:26] Uh huh. So don't bring up network automatically using Debian tools. [12:26] Remove 'auto' from /etc/network/interfaces [12:27] But only for eth*. You still want your loopback device setup ;-) [12:28] Yes yes [12:29] wasabi, And put what in its place (I gather that is the same thing as disabling roaming mode in networksettings? [12:29] Use network manager. [12:29] Completely bypasses that. [12:29] OK. [12:30] But is there a way to make sure that it still happens upon entering gnome? [12:30] I'd like the roaming features, works great, just not while booting. [12:30] Hmm? [12:30] That's what network manager is for. [12:31] Ok, Then tell me should roaming be on or off? [12:32] Eruantalon: What do you mean by "roaming mode", switching automatically between available wireless networks? [12:32] mbiebl, yes. But it is not my expression it says that in network settings [12:32] I don't even know what screen you are refering to. [12:33] Eruantalon: If you are using wireless, network-manager is indeed the best choice for you. [12:33] Ok just to make sure that we are talking about the same thing... What network manager are you talking about? [12:33] Just make sure, you comment all all eth* entries in /etc/network/interfaces [12:34] apt-get install network-manager-gnome [12:34] The only one of all of the solutions named "network manager" [12:34] and what command opens it? [12:34] It adds itself to your session. Install it, log out, then back in. [12:35] mbiebl, I am using both wireless and wired( because sometimes wireles is to slow) [12:35] Or run "nm-applet" [12:35] Better: "nm-applet --sm-disable" [12:35] What's sm-disable do? [12:35] wasabi, Ok, That is the same thing as what i've already got [12:35] Otherwise you will have two nm-applet instances nextt time you log in. [12:36] Eruantalon: Okay, and what's wrong with it? [12:36] Eruantalon: Have you read /usr/share/doc/network-manager/README.Debian? [12:36] 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] Nope, it's not. [12:37] It does not block boot. [12:37] Again, Debian network infrastructure does that. [12:37] Again, comment out the auto lines for eth* in /etc/network/interfaces [12:37] wasabi, And put nothing instead? [12:37] yes. [12:37] I'm about done with this. [12:38] And that will make sure nothing network related is started until gnome is? [12:38] No. It will not make sure of that. [12:38] Thanks a bunch anyway [12:38] It will not use Debian's network infrastructure to start dhclient and block on it. That is all it will do. [12:38] If you have other pieces of software which block on the network, you'll need to fix those. [12:38] Such as for instance mounting network file systems in fstab. [12:38] Also, as soon as the network manager daemon is started, it goes off and starts dhclient, in the background. [12:40] Well I've commented out the two auto's and I guess I will have to restart to see what happens. Thanks. [12:40] Do not comment out auto lo [12:40] As mbiebl said earlier. [12:40] I haven't :-) [12:41] Eruantalon: please pastebin your /etc/network/interfaces [12:41] ok two seconds [12:42] http://paste.ubuntu-nl.org/32977/ [12:43] Ok? [12:43] You have the wireless interfaces set to auto also. [12:43] You'll want to disable them too. [12:43] The idea is whatever you set to auto and dhcp results in dhclient being started at boot, and waiting. [12:43] everything but lo ? [12:44] Correct. [12:44] thanks === tck [n=tck@213-202-161-88.bas503.dsl.esat.net] has joined #upstart [12:44] Eruantalon: you can remove everything besides [12:44] auto lo [12:44] iface lo inet loopback [12:45] without screwing anything up? [12:45] If you have NM, you are fine. [12:46] But this is getting mighty OT now. [12:46] 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] mbiebl, Sorry, But I thought it was something upstart would be able to do simply- === Eruantalon [n=hans@5634185c.rev.stofanet.dk] has joined #upstart [12:49] Thanks. That did the trick [12:50] Eruantalon: the main idea behind upstart is, that it is event based. [12:50] yep [12:50] You still need sources, which generate these events. [12:51] NM could be such a source for network events. [12:51] mbiebl, I just thought that upstart was the underlying thing that drove network manager [12:52] 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] Well, upstart is mainly a event queue and dispatcher. [12:52] It has no knowledge about network and stuff. [12:53] That's what I meant, when I said these kind of events have to be feed into upstart from external sources. === tck [n=tck@213-202-161-88.bas503.dsl.esat.net] has joined #upstart [12:54] Hmm I gotta reboot to check something. It seems that network manager lost any information about my wireless card... === 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 [12:04] 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 === Amaranth_ [n=travis@ubuntu/member/Amaranth] has joined #upstart === mbiebl [n=michael@e180070127.adsl.alicedsl.de] has joined #upstart [01:10] AlexExtreme: no idea, sorry [01:10] I would imagine so [01:11] ok, thanks [01:11] also, one more Q: do you plan to get native upstart jobs into gutsy? [01:11] no === 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