On 4/12/21 9:56 AM, Valeri Galtsev wrote: > > > On 4/12/21 8:34 AM, Johnny Hughes wrote: >> On 4/11/21 11:32 AM, Kenneth Porter wrote: >>> I'm yum updating some CentOS 7 systems today and got this error. Two >>> systems (so far) seem to have rebooted fine. Should I worry? >>> >>> error: file /etc/ld.so.conf.d/kernel-3.10.0-1127.19.1.el7.x86_64.conf: >>> No such file or directory >> >> The kernel does does contain that file. In CentOS linux 7 (and 8), the >> file is actually blank .. well is has one comment line: >> >> # Placeholder file, no vDSO hwcap entries used in this kernel. >> >> >> If you want the error to go away, just as the root user, do: >> >> touch /etc/ld.so.conf.d/kernel-3.10.0-1127.19.1.el7.x86_64.conf >> chmod 444 /etc/ld.so.conf.d/kernel-3.10.0-1127.19.1.el7.x86_64.conf >> >> The above 2 commands should create a zero size file there and prevent >> the error. >> >> As to how you got the error .. it seems there is an issue with the >> kernel-3.10.0-1127.19.1.el7.x86_64 install on your machine, it is at >> least missing that file. If you are using that kernel .. you might want >> to re-install it instead to make sure all the files are there. There is >> a newer kernel released for EL7. >> >> As to the purpose of /etc/ld.so.conf.d/, info here: >> >> https://linux.101hacks.com/unix/ldconfig/ >> > > That is the general description of ldconfig, which is transparent and > clear as to what ldconfig purpose is. > > What is puzzling for me (I'm sure you are answering my question): why > anything related to kernel package should be needed for automatically > searching for shared libraries to be loaded (when one uses anything > linked to shared libraries)? What kernel package brings that can have > anything to do with that??! > > Thanks for insights! > > Valeri > Well, that is a good question, since the kernel boot starts very early in the process. I suppose it is possible that some hardware drivers for kernel modules MIGHT need a path to external shared libraries. All I know for sure is that the capability to have an external ldconfig path exists for the kernel (ie, it is built in). I do not ever remember this being actually populated. But the capability has existed for a long time.