From what I understand, directories such as /usr/lib and stuff are properly used even in case of a corrupted ld.so cache. like ldconfig does not affect those directories at this time.
W dniu 20.05.2016 o 14:06, Vasiliy Tolstov pisze: > 2016-05-20 15:01 GMT+03:00 Florian Weimer <fwei...@redhat.com>: >> The default systemd configuration runs ldconfig at boot. Why? >> >> Most deployments of systemd appear to be dynamically linked, so if the ld.so >> caches are corrupted, you will never get to the point where you can run >> ldconfig. >> >> Running ldconfig too early tends to cause problems because the file system >> might not have been set up completely, and the cache does not match what the >> system administrator has configured. >> >> Florian > > > Also sometimes this take on my server 22s =) >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
