You are not logged in.
ok, i googled, searched the forums, learned whatever i could about ldconfig. however - if i understand correctly, there is NO real advantage in running it every single system startup... maybe only after main packages install, like KDE, Gnome, etc... if this is so, why not remove the 10-seconds-delay (ie, ldconfig ) from startup to pacman PKGBUILDs ?
Offline
or modify the rc.sysinit script with :
stat_busy "Updating Shared Library Links"
/sbin/ldconfig &
stat_done
Offline
true. but the question still remains - what is the reason for having ldconfig running each startup and not in PKGBUILDs?
Offline
true. but the question still remains - what is the reason for having ldconfig running each startup and not in PKGBUILDs?
it's a catch all - prevents errors from someone NOT doing it in a PKGBUILD....
maybe pacman can run it after the post_install step.. I dunno.
personally I reboot like once every 1-3 weeks, so I could care less. And I usually reboot remotely and just wait for sshd to start back up
Offline
maybe pacman can run it after the post_install step.. I dunno.
FYI, pacman is calling "ldconfig" each time a package is installed or removed.
There's no need to add ldconfig calls in post_XXX functions.
Offline
phrakture wrote:maybe pacman can run it after the post_install step.. I dunno.
FYI, pacman is calling "ldconfig" each time a package is installed or removed.
There's no need to add ldconfig calls in post_XXX functions.
huh, I was not aware of this - guess I never paid attention. I wasn't suggesting IN the post_install/remove... but after it - in the pacman portion itself
Offline
Pacman does ldconfig after installing packages, as it should do. Doing ldconfig at boot just takes 2 or 3 seconds on my slow hd, so for me it's not worth disabling. If it takes 10 seconds then you should really disable it at bootup. (or go check what's wrong with your system: no dma? ;-)
Offline
actually, if u bring this up... i have a sata drive, which hdpram refuses to work with under Arch... with slackware which installed on another partition all works fine. and i doubt the ldconfig takes so long becuase of that btw, since nothing else lags. my hdparm output :
[root@arch tmp]# hdparm /dev/sda
/dev/sda:
HDIO_GET_MULTCOUNT failed: Operation not supported
IO_support = 0 (default 16-bit)
readonly = 0 (off)
readahead = 256 (on)
geometry = 14593/255/63, sectors = 120034123776, start = 0
i have tried it with my current (2.6) kernel (customized+nitro2) and the stock kernel - same results. google didnt provide too much help either...
Offline
actually, if u bring this up... i have a sata drive, which hdpram refuses to work with under Arch... with slackware which installed on another partition all works fine. and i doubt the ldconfig takes so long becuase of that btw, since nothing else lags. my hdparm output :
[root@arch tmp]# hdparm /dev/sda /dev/sda: HDIO_GET_MULTCOUNT failed: Operation not supported IO_support = 0 (default 16-bit) readonly = 0 (off) readahead = 256 (on) geometry = 14593/255/63, sectors = 120034123776, start = 0
i have tried it with my current (2.6) kernel (customized+nitro2) and the stock kernel - same results. google didnt provide too much help either...
compare the hdparm binaries then - mount the slackware partition and run that from arch... if it still doesn't work it may be a library problem (which could cause some ldconfig problems too...)
I agree that my ldconfig probably takes 3 seconds or so - I'm all up for optimzation and everything, but come on, we're talking an additional 5-10 seconds to startup... get a glass of water or something during that time.
Offline
tnx for the advice. same results however :
[root@arch sbin]# pwd
/mnt/usr/sbin
[root@arch sbin]# ./hdparm /dev/sda
/dev/sda:
HDIO_GET_MULTCOUNT failed: Operation not supported
IO_support = 0 (default 16-bit)
readonly = 0 (off)
readahead = 256 (on)
geometry = 14593/255/63, sectors = 120034123776, start = 0
[EDIT]
and it seems im not the only one... : http://marc.free.net.ph/message/2004102 … 95983.html
Offline
regarding the hdparm, it seems it doesnt support scsi nor sata. it only works on my slackware kernel since its still using ide-sata module thus treat the sata as ide plus ide naming - its /dev/sda on my arch, and /dev/hde on my slack...
back to ldconfig.
Pacman does ldconfig after installing packages, as it should do.
even better - why is it executed on each boot then?
Offline
Someone made a (save) choice somewhere, that's all. If it bothers you then just remove it.
Offline
Offline
Ok,
this is nice to know ... now I don't need to add it anymore to PKGBUILDS ...
although maybe there should be a variable or so that lets pacman know that it should run ldconfig ... since I suppose that running it once for a set of packages is enough ... anyway, the current situation is also "sufficient" ...
Offline