Slackware This 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.
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.
|
 |
01-20-2006, 06:36 PM
|
#1
|
LQ Newbie
Registered: Jan 2006
Posts: 10
Rep:
|
Slackware 10.2 - /sbin/ldconfig - How to disable at boot time?
Hi all,
For Slackware 10.2, ldconfig is running at boot-up, and this makes the boot process somewhat slow. I was wondering if anyone knew where (or in what script) /sbin/ldconfig is being called on boot-up so I can disable it. Thanks for your input everyone.
IntoX
|
|
|
01-20-2006, 06:39 PM
|
#2
|
Senior Member
Registered: Apr 2002
Location: Arbovale, WV
Distribution: Slackware
Posts: 1,761
Rep:
|
Edit the /etc/rc.d/rc.M and uncomment the lines:
if [ -x /sbin/ldconfig ]; then
echo "Updating shared library links: /sbin/ldconfig"
/sbin/ldconfig
|
|
|
01-20-2006, 06:39 PM
|
#3
|
Senior Member
Registered: Apr 2002
Location: Arbovale, WV
Distribution: Slackware
Posts: 1,761
Rep:
|
Forgot to mention, all the boot time scripts and commands are in the /etc/rc.d directory.
|
|
|
01-20-2006, 08:04 PM
|
#4
|
LQ Newbie
Registered: Jan 2006
Posts: 10
Original Poster
Rep:
|
Thanks Tangle
Thanks Tangle, I will try that now...
IntoX
PS: I had forgotten to look in /etc/rc.d/rc.M, which going back through the SlackBook, I realize now I should have went there first  I trudged through rc.S first, expecting it there. Hmm...
Last edited by intox; 01-20-2006 at 08:07 PM.
|
|
|
01-20-2006, 08:15 PM
|
#5
|
Senior Member
Registered: Apr 2002
Location: Arbovale, WV
Distribution: Slackware
Posts: 1,761
Rep:
|
You can use the command:
cat /etc/rc.d/rc.M | grep ldconfig
to find the string.
cat just prints the contents of the file to the screen.
| pipes (transfers) the data to the command after the |
grep finds and line that has ldconfig in it.
This a useful command.
|
|
|
01-20-2006, 08:27 PM
|
#6
|
LQ Newbie
Registered: Jan 2006
Posts: 10
Original Poster
Rep:
|
Again, Thanks
It works. Woohoo.
IntoX
|
|
|
01-20-2006, 08:32 PM
|
#7
|
LQ Newbie
Registered: Jan 2006
Posts: 10
Original Poster
Rep:
|
On grep
I was trying to remember some cool things with grep, which was part of the reason why I didn't find anything on ldconfig in /etc/rc.d/, but I just remembered I could have done
$ grep ldconfig /etc/rc.d/*
To find all files with ldconfig in them, and then gone from there...
IntoX
|
|
|
01-20-2006, 09:49 PM
|
#8
|
LQ Guru
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,852
|
Are you going to run it from cron instead?
|
|
|
01-21-2006, 08:48 AM
|
#9
|
LQ Guru
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,234
|
You can change ldconfig to run in the background to speed up booting by adding a "&" at the end of the command: in rc.M
Code:
if [ -x /sbin/ldconfig ]; then
echo "Updating shared library links: /sbin/ldconfig"
/sbin/ldconfig &
|
|
|
01-21-2006, 10:39 AM
|
#10
|
Member
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current, SlackwareARM-15.0
Posts: 835
Rep:
|
Another possibility is to comment the ldconfig stuff in /etc/rc.d/rc.M as suggested above, and run it 5 minutes after boot, by adding the following lines in /etc/rc.d/rc.local
Code:
/usr/bin/echo "ldconfig" | /usr/bin/at now +5minutes 2> /dev/null 1> /dev/null
echo "at: /sbin/ldconfig will be started after 5 minutes..."
Don't forget to make rc.local executable, if it isn't yet
Code:
chmod +x /etc/rc.d/rc.local
Cheers, Leon.
Last edited by BroX; 01-21-2006 at 10:42 AM.
|
|
|
01-21-2006, 07:34 PM
|
#11
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482
|
Just another tidbit, in /etc/rc.d/rc.M, just below the lines to run ldconfig, is a line to run fc-cache. Unless you are playing with fonts, you probably do not need that line at boot-up either.
|
|
|
01-22-2006, 01:39 AM
|
#12
|
LQ Newbie
Registered: Jan 2006
Posts: 10
Original Poster
Rep:
|
Thos e are excellent suggestions!
You guys bring up valid points in the streamlining of the boot process by either running it in cron, with the & after it, or with a script that runs it later. I can't believe I havent thought of &, but I will give those options a try and then report on the performance issues I have. Thank you all for you suggestions!
IntoX
|
|
|
01-22-2006, 10:53 AM
|
#13
|
Member
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current, SlackwareARM-15.0
Posts: 835
Rep:
|
|
|
|
All times are GMT -5. The time now is 11:02 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
|
|