Arch Linux

tezem

Member

Registered: 2004-11-04

Posts: 51

Website

ldconfig behavior of Arch

The time which is needed on every boot for the ldconfig isn't acceptable for me because this is the one out of all my init scripts, which takes the biggest time.
So I would like start a discussion of the meaningfullness of this or if there would be other ways to handle the library update properly.
The most perfect solution I could think of would be to build the update directly into pacman.
It should be only updated when new libs are installed.
When somebody install libs not with pacman he has to do it manually.
Is this idea bad? Is it not possible?
What do you say?

wdemoss

Member

From: WV - USA

Registered: 2004-01-18

Posts: 222

Re: ldconfig behavior of Arch

I believe this has been brought up before, and if i'm not mistaken, pacman does run ldconfig after it finishes updating packages. If you don't want ldconfig on boot up comment it out (I have) and all is well.

---

Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?

Dusty

Schwag Merchant

From: Medicine Hat, Alberta, Canada

Registered: 2004-01-18

Posts: 5,986

Website

Re: ldconfig behavior of Arch

Yes, this has been discussed. Some people have commented out the lines in the init scripts that update the shared libraries (it works for me). I'm also pretty sure pacman already does update the library path when it installs a new library. To be honest, I don't know why its done on bootup. You can probably safely comment out those lines with no bad effects. If there are any, mention them here.

I think it was originally discussed in the context of this big thread:

http://bbs.archlinux.org/viewtopic.php?t=8490

Dusty

---

** Arch Linux Apparel and more ** Arch Linux stickers, laptop bags, jewelery ** I wrote a book on Python 3 ** and one on mental health **