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.
hi,
is it necessary to run ldconfig at boot? i only had to run that a few times while building linux from scratch.
how can i prevent slack from running ldconfig at boot?
thanks.
DESCRIPTION
ldconfig creates the necessary links and cache to the most
recent shared libraries found in the directories specified
on the command line, in the file /etc/ld.so.conf, and in
the trusted directories (/lib and /usr/lib). The cache is
used by the run-time linker, ld.so or ld-linux.so. ldcon_
fig checks the header and file names of the libraries it
encounters when determining which versions should have
their links updated.
Speculate: If you do not run ldconfig at boot time, I would think that the dynamicly link (compiled) program would not run (correctly).
However if you insist to disable it at boot time:
cd /etc/rc.d
emacs rc.M
and comment out
Code:
# Update all the shared library links:
if [ -x /sbin/ldconfig ]; then
echo "Updating shared library links: /sbin/ldconfig"
/sbin/ldconfig
fi
You can disable ildconfig at boot, the only thing you will have to remember is to run ldconfig after installing or uninstalling software which provides shared libraries. It isn't always necessary but it doesn't harm running ldconfig when it's not needed.
hi,
reducing boot time is the only reason i want to disable ldconfig at boot. i also want to disable hotplug at boot, maybe saving another 10 seconds . making /etc/rc.d/rc.hotplug non-executable is not as flexible as passing "nohotplug" to kernel, but for some reason, the "nohotplug" way fails and i still don't know how to fix it. see if you can help me here: http://www.linuxquestions.org/questi...readid=199149.
thanks.
I indeed disabled hotplug as well as ldconfig but I put ldconfig at rc.0. This way the shutdown processes is slower but I don't care because I just leave my computer alone to do this job
It makes a huge difference disabling ldconfig + hotplug at boot up (and I still don't get what exactly hotplug does, my usb mass storage are detected without hotplug).
There's no need to set any "olympic record" but saving 15-20 secs. it's important if you use your computer as a desktop one.
Bye
SnOp
PD: my computer boots on about 40 secs until reaching xfce .
I also have disabled ldconfig at boot - doesn't produce problems and I run it after I install new software.
While you're at it you may want to disable fc-cache as well, since you probably aren't adding a lot of fonts every day.
Why save time on the boot? I use Slackware on my laptop and am turning it on and off and moving around with it frequently. So each boot is worth saving some time on.
Originally posted by coffeedrinker While you're at it you may want to disable fc-cache as well, since you probably aren't adding a lot of fonts every day.
i was gonna get to that, too. i haven't because fc-cache doesn't take as long as it used to (total boot time now is about 15 seconds with fc-cache). but in case it starts to slow again, how do i disable it?
Quote:
Why save time on the boot? I use Slackware on my laptop and am turning it on and off and moving around with it frequently. So each boot is worth saving some time on.
yeah. and i'm waiting for kexec to stablize to give it a try. it's supposed to make it possible to skip reboot altogether.
thanks.
Originally posted by equinox u people amaze me, i gave u the correct option, instead of chmodding files and screwing around just run
Code:
pkgtool
i guess that's a more obvious way to do it, but that doesn't mean the other ways are wrong. in fact, i left mdk for slk because i wanted to force myself to skip the gui's and learn what really happens, at least once.
i guess that's a more obvious way to do it, but that doesn't mean the other ways are wrong. in fact, i left mdk for slk because i wanted to force myself to skip the gui's and learn what really happens, at least once.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.