Increase boot times: have hotplug run in background?
SlackwareThis Forum is for the discussion of Slackware 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.
Increase boot times: have hotplug run in background?
Howdy, just wondering if it would be safe for me to have hotplug run in the background when I'm booting up, so that the system isn't hung up on that one process as I'm booting up (currently it takes up over 20 seconds, and my boot speed time is somewhere around 80 seconds.) So I was just wondering if you guys thought it would be a safe move to just put an & after the command to initiate hotplug when the system boots or not (hopefully this will mean I'll get a boot time that's a little faster)
Nope it's not a good idea because maybe (99% sure) you then run a service that actually needs what's being detected by hotplug.
An alternative idea (which is fast) is to disable hotplug and modprobe all the modules you need manually or make a big kernel with all you need built-in.
Originally posted by gbonvehi Nope it's not a good idea because maybe (99% sure) you then run a service that actually needs what's being detected by hotplug.
An alternative idea (which is fast) is to disable hotplug and modprobe all the modules you need manually or make a big kernel with all you need built-in.
How about modprobe the modules that I need usually (right now I have usb interface, alsa, and graphics drivers loaded) and then have Hotplug load afterward? Does hotplug even load for rl1?
you can try disabling hotplug at startup (chmod -x). if it doesn't cause any prob at startup (it didn't for me), then i think it'll be safe to run it in background during startup.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.