how do i let dhclient3 run at a later runlevel with concurrency active?
DebianThis forum is for the discussion of Debian Linux.
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.
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.
Distribution: Debian Etch 2.6.18-(custom compile for k7) with a 72 no 58 no 42 second bootup time (XP=4mins)
Posts: 52
Rep:
how do i let dhclient3 run at a later runlevel with concurrency active?
Hi guys,
I followed this guide to speed up my boot time, and i got significant improvements. My latest bootchart shows 42sec boot time which I'm really happy with and people in my family might start using it cos it takes about 4 minutes to be able to run a program in XP from boot. One thing that is bothering me though is the huge amount of time wasted while my system is doing dhcp requests. I have a wireless pci card and it just isn't fast. I've run the option Concurrency=shell i'm just trying to figure out how to get dhclient3 to do whatever it has to while say gdm and xorg are loading. I'm running debian etch kernel 2.6.18 (custom compile).
I don't know how it could be done within the parameters you set, but if it is a DHCP request that is taking long, why not remove the DHCP part of it, and assign a static address on the computer?
I've never played with a fast boot, but on default booting, machine with static addresses set on themselves take much less time than DHCP set addresses.
You can't post any pics here on LQ, so the way to deal with a picture is to post it on one of your machines and give a link, or put it on a free picture site, and again give a link.
Although to be honest, seeing a picture of how long your boot takes is unnecessary for us.
Distribution: Debian Etch 2.6.18-(custom compile for k7) with a 72 no 58 no 42 second bootup time (XP=4mins)
Posts: 52
Original Poster
Rep:
Is there any way to simply move it to a different run level though?
I've tried everything to get it to be a static ip and i just can't do it. My router does allow it because in windows xp it works a treat but i've followed the various guides regarding the ./networking/interfaces file and can't do it. Nonetheless, it could dhcp its heart away if it was doing other things at the same time.
You don't mean a different run level. Runlevels are 1, 2, 3, 4, 5, and 6, and just categorize what programs start within their parameters. What you are looking for is the tool update-rc.d. Use the manpage.
Problem is, dhclient isn't listed specifically in the startup scripts in /etc/rcX.d. It is part of some other process, and likely can't easily be called earlier.
It is far easier to simply give the machine a static address. It will take less than 60 seconds to do, and it will work flawlessly, allowing a much faster boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.