net.wlan0 improvement

Message

Kobboi · Post by **Kobboi** » Tue Oct 16, 2007 6:36 pm

I have a wireless card that uses its Windows driver through ndiswrapper. Almost all of the time, when /etc/init.d/net.wlan0 starts, it does not find any access point to associate with. After logging into Gnome, I have to change to root to restart the script and all works well after that. Any idea on how to improve this way of working?

no_hope · Post by **no_hope** » Tue Oct 16, 2007 7:36 pm

/etc/init.d/net?

Kobboi · Post by **Kobboi** » Wed Oct 17, 2007 8:18 am

I guess you mean /etc/conf.d/net? There is an option to timeout the association but I don't know if that's what I'm looking for. For the moment it doesn't wait 60 seconds (the default) before aborting. On the other side, I don't want my booting to freeze on wireless discovery.

Gentree · Post by **Gentree** » Wed Oct 17, 2007 9:34 am

Kobboi wrote:I guess you mean /etc/conf.d/net? There is an option to timeout the association but I don't know if that's what I'm looking for. For the moment it doesn't wait 60 seconds (the default) before aborting. On the other side, I don't want my booting to freeze on wireless discovery.

so dont put wireless in boot. Unless booting your system is somehow dependant on the network it should not be in the boot run level.

no_hope · Post by **no_hope** » Wed Oct 17, 2007 2:34 pm

Kobboi wrote:I guess you mean /etc/conf.d/net? There is an option to timeout the association but I don't know if that's what I'm looking for. For the moment it doesn't wait 60 seconds (the default) before aborting. On the other side, I don't want my booting to freeze on wireless discovery.

Sorry, my bad. I meant post your /etc/conf.d/net.

If you emerge ifplugd, the net init script won't block your boot process.

Kobboi · Post by **Kobboi** » Wed Oct 17, 2007 5:09 pm

Gentree wrote:
Kobboi wrote:I guess you mean /etc/conf.d/net? There is an option to timeout the association but I don't know if that's what I'm looking for. For the moment it doesn't wait 60 seconds (the default) before aborting. On the other side, I don't want my booting to freeze on wireless discovery.
so dont put wireless in boot. Unless booting your system is somehow dependant on the network it should not be in the boot run level.

I used "booting" as a general term for normal system startup. It's in the default runlevel.

Gentree · Post by **Gentree** » Wed Oct 17, 2007 5:27 pm

OK, it's always helpful to use correct terminology when describing a problem. It helps to get you correct replies.

Code: Select all

Any idea on how to improve this way of working?

Probably best to take it out of default as well if it holds things up. You can always start it explicitly with

Code: Select all

 /etc/init.d/.....   start

. Either as an icon when you need it to fire up or using what ever startup mechanism there is on gnome.

That way you dont need to wait for it to fininsh.