Hi, Thomas Besser writes:
> [...] > As far as I understand, package libc-bin registers dpkg (?) triggers > scripts which are executed on every update of any package. > > How can I find out, which trigger script of libc-bin causes this error? > There must be a place, where dpkg stores this scripts. But where? The trigger definition for libc-bin is in /var/lib/dpkg/info/libc-bin.triggers On my machine it says $ cat /var/lib/dpkg/info/libc-bin.triggers interest ldconfig I am not sure what exactly this does, but I *guess* it triggers updating of /etc/ld.so.cache by running the ldconfig command in some way. IIRC, the error you posted earlier looked a lot like it came from a piece of Perl code but I have no idea where it would come from. My /sbin/ldconfig is a shell script wrapper that handles triggers via dpkg-trigger, an ELF binary, and passes the buck to /sbin/ldconfig.real, also an ELF binary. Both are unlikely to be directly responsible for the error message you posted. # Running Devuan jessie, BTW. I know it doesn't answer your question completely but hope this helps anyway, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
