Re: Delayed ldconfig execution in postinst step
>>>>> "Goswin" == Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> writes:
>> - there are no dangerous transitions (libc5->libc6) that would
>> require having updated ld.so.cache immediately - all
>> applications should follow the ld.so.conf paths if something is
>> not in the cache. No problem here.
I am not convinced this is correct.
Once I installed a corrupt libc6 package (without realizing it was
corrupt), and my system was stuffed. Not because libc6 itself was
corrupt. The problem was because ldconfig wasn't run, and this meant I
couldn't run any executables that required libc6.
Eventually I was able to run ldconfig from a preexisting chroot, and
my system was fine.
Maybe it has changed now, but it didn't look like the applications
were falling back to ld.so.conf when this happened.
--
Brian May <bam@debian.org>
Reply to: