Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-07-2004, 02:40 PM
|
#1
|
Member
Registered: Jun 2002
Location: Where ever the Navy sends me
Distribution: Gentoo
Posts: 320
Rep:
|
eth0 causes looooong boot time
Hey folks
I currently have my deafult network interface disabled at boot time. Here's why; my main machine is a laptop and I use it in different situations a lot. If I have the eth0 interface set to start on boot and I have the network unplugged, it takes about 5 minutes for it to realize this and continue booting. Is there a way to cut back the time it takes for the computer to boot without having to set eth0 to not start at boot.
|
|
|
11-07-2004, 04:02 PM
|
#2
|
Member
Registered: Apr 2004
Location: Copenhagen, Denmark
Distribution: Gentoo + Debian PPC
Posts: 44
Rep:
|
Well, you could edit your /etc/dhclient.conf and add a timeout; thats what I do on my laptop.
For instance
timeout 10;
gives the client ten seconds to get an offer and then lets the boot carry on.
Hope this helps
|
|
|
11-07-2004, 04:47 PM
|
#3
|
Member
Registered: Jun 2002
Location: Where ever the Navy sends me
Distribution: Gentoo
Posts: 320
Original Poster
Rep:
|
it seems that I don't have this file, should I add it to make it do a 10 sec timeout?
|
|
|
11-07-2004, 04:52 PM
|
#4
|
Member
Registered: Jun 2002
Location: Where ever the Navy sends me
Distribution: Gentoo
Posts: 320
Original Poster
Rep:
|
I added it and it didn't do anything, any other ideas?
|
|
|
11-07-2004, 05:28 PM
|
#5
|
LQ Newbie
Registered: Oct 2003
Distribution: Gentoo
Posts: 13
Rep:
|
Assuming you're using DHCP, try opening /etc/sysconfig/network if it exists, and adding the line "DHCP_TIMEOUT=10" (or however many seconds you'd like).
It varies a little between different distros, so if that doesn't work, what are you running?
|
|
|
11-07-2004, 05:30 PM
|
#6
|
Member
Registered: Jun 2002
Location: Where ever the Navy sends me
Distribution: Gentoo
Posts: 320
Original Poster
Rep:
|
I use /etc/sysconf/network all the time. I will try adding that there and see what happens. My laptop is running MDK 10.0 with a lot of updates.
|
|
|
11-07-2004, 06:16 PM
|
#7
|
Member
Registered: Jun 2002
Location: Where ever the Navy sends me
Distribution: Gentoo
Posts: 320
Original Poster
Rep:
|
That didn't do a thing, any more ideas that could solve this?
|
|
|
11-07-2004, 06:28 PM
|
#8
|
LQ Newbie
Registered: Oct 2003
Distribution: Gentoo
Posts: 13
Rep:
|
If I remember right, the /sbin/ifup script starts the network interfaces, and calls the dhcpcd program from it. You could try searching through the file and if you see dhcpcd being called, add "-t 10" after it (for a timeout of 10 seconds).
Otherwise, sorry, out of ideas...
|
|
|
11-07-2004, 06:48 PM
|
#9
|
Member
Registered: Nov 2000
Location: Hermon, ME
Distribution: slackware
Posts: 201
Rep:
|
If you check out this page it tells you how to configure your dhcp:
http://www.whitefang.com/dhcp-agent/...p-agent_2.html
About halfway down is a section that says configureable variables nad it has a section Client Configuration Variable: dhcp-discovery-retries . I think this will force it not to try so long.
|
|
|
11-07-2004, 08:46 PM
|
#10
|
LQ Newbie
Registered: Jun 2003
Location: Gonzaga University
Distribution: Slackware, RHEL
Posts: 23
Rep:
|
Quote:
Originally posted by faralen
If I remember right, the /sbin/ifup script starts the network interfaces, and calls the dhcpcd program from it. You could try searching through the file and if you see dhcpcd being called, add "-t 10" after it (for a timeout of 10 seconds).
Otherwise, sorry, out of ideas...
|
faralen is right, I did this exact thing on my laptop. It works.
|
|
|
11-07-2004, 09:29 PM
|
#11
|
LQ Newbie
Registered: Apr 2004
Distribution: Kubuntu
Posts: 11
Rep:
|
I use Mandrake with sbc dsl and I was having this problem too. I found a webpage and they said to:
eth0 fails to start: Try removing the "/etc/sysconfig/network-scripts/ifcfg-eth0" file.
I did that and everything worked perfect after that. I found it at http://users.dslextreme.com/~craig.l...notes/dsl.html
|
|
|
All times are GMT -5. The time now is 08:17 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|