Bug#72140: Setting up libraries too slow

[nveber@primusolutions.net]

On Sat, Sep 23, 2000 at 01:05:24AM -0700, Jim Lynch wrote:
> Hi, 
> 
> Summary: Don't even play with this. If ldconfig takes too long for you, go
> have lunch. My preference and vote is for stability: installation of shared
> libs need to run ldconfig.
> 
> ---
> 
> I guess you're not getting the full story about the ld.so and its cache:
> if it doesn't exist, you can't even find libc. 
> 
> If you can't find libc or any other lib, your system becomes unusable
> until you get to the point of being able to run ldconfig... 
> 
> Getting to this point is a VERY large hassle.
> 
> I know... because I had to do it myself, my motherboard was flaky and some-
> how the cache was getting corrupted, rendering my system totally unusable.
> 
> Can a plain user who doesn't understand the intricacies of the boot process
> be reasonably expected to do this? Tell ya what: remove the cache file and
> see what you have to do to restore it.
> 
> (non-hint: if you don't know, it will take you a LONG time to get your 
> system back. Don't do this on a production server.)

Wow, that was tough! :)

root@pyre[/etc]# pwd
/etc
root@pyre[/etc]# ls -al ld.so.c*
-rw-r--r--    1 root     root        17417 Sep 23 13:37 ld.so.cache
-rw-r--r--    1 root     root          132 Sep 23 13:37 ld.so.conf
-rw-r--r--    1 root     root          132 Mar 30  1999 ld.so.conf.old
root@pyre[/etc]# rm ld.so.cache
root@pyre[/etc]# id
uid=0(root) gid=0(root) groups=0(root)
root@pyre[/etc]# ls ld.so.c*
ld.so.conf  ld.so.conf.old
root@pyre[/etc]# ldconfig
ldconfig: warning: can't open /usr/X11R6/lib/libwine.so (No such file or
directory), skipping
ldconfig: warning: can't open /usr/lib/i486-linuxaout/libdb.so.1 (No such
file or directory), skipping
ldconfig: warning: can't open /usr/lib/libtcl7.6.so (No such file or
directory), skipping
ldconfig: warning: can't open /usr/lib/libgmodule-1.1.so.3 (No such file or
directory), skipping
ldconfig: warning: can't open /usr/lib/libglib-1.1.so.3 (No such file or
directory), skipping
root@pyre[/etc]# ls -al ld.so.*
-rw-r--r--    1 root     root        17417 Sep 23 13:39 ld.so.cache
-rw-r--r--    1 root     root          132 Sep 23 13:37 ld.so.conf
-rw-r--r--    1 root     root          132 Mar 30  1999 ld.so.conf.old




Perhaps your are confusing ld.so.cache with /lib/libc.so.6.  I agree that
recovering from a screwed up libc is not fun, but I've done that also in the
past.