You are not logged in.
Pages: 1
I have minutes long boot delays because every time there is "Rebuild Dynamic Linker Cache...", apparently caused by ldconfig.service. According to this thread, the service can be safely disabled because ldconfig is automatically run by pacman. The solution suggested was
sudo systemctl disable ldconfig
sudo systemctl stop ldconfigUnfortunately it doesn't work for me, I still see rebuild happening (and `systemctl status ldconfig` saying "active" after having booted). Any ideas?
Last edited by Hi-Angel (2020-07-24 07:05:59)
Offline
I have minutes long boot delays because every time there is "Rebuild Dynamic Linker Cache...", apparently caused by ldconfig.service. According to this thread, the service can be safely disabled because ldconfig is automatically run by pacman. The solution suggested was
sudo systemctl disable ldconfig sudo systemctl stop ldconfigUnfortunately it doesn't work for me, I still see rebuild happening (and `systemctl status ldconfig` saying "active" after having booted). Any ideas?
That service does the following checkups:
ConditionNeedsUpdate=/etc
ConditionFileNotEmpty=/etc/ld.so.cacheIt shouldn't be running on each boot unless you do something on /etc or clear /etc/ld.so.cache...
Do you update each day or something?
Post the output of 'pacman -Q | wc -l', having a lot of packages and doing frequent updates can cause this issue...
Last edited by GaKu999 (2020-07-24 07:14:15)
Offline
It shouldn't be running on each boot unless you do something on /etc or clear /etc/ld.so.cache...
Do you update each day or something?
Well, I should mention that I try to reboot as rare as possible, maybe once or twice a week.
But no, I don't update things too often. In between these boots I may often install some small package (and maybe even delete it afterwards), which apparently triggers the service. Like for example right now I installed `lsscsi` because colleague asked me to check something on my laptop.
Post the output of 'pacman -Q | wc -l', having a lot of packages and doing frequent updates can cause this issue...
$ pacman -Q | wc -l
2443Last edited by Hi-Angel (2020-07-24 07:52:36)
Offline
GaKu999 wrote:It shouldn't be running on each boot unless you do something on /etc or clear /etc/ld.so.cache...
Do you update each day or something?Well, I should mention that I try to reboot as rare as possible, maybe once or twice a week.
But no, I don't update things too often. In between these boots I may often install some small package (and maybe even delete it afterwards), which apparently triggers the service. Like for example right now I installed `lsscsi` because colleague asked me to check something on my laptop.
GaKu999 wrote:Post the output of 'pacman -Q | wc -l', having a lot of packages and doing frequent updates can cause this issue...
$ pacman -Q | wc -l 2443
Yep, that's a LOT of packages....and yeah, tiny installations can do that...
While pacman does the work, sometimes systemd still tells that service to start...
Shouldn't be a thing because you disabled it...but maybe something changed on systemd.
If you really want to disable that service, at the potential price of the side effects you can use 'systemctl mask ldconfig.service'...
Offline
Pages: 1