Some binaries are failing since the last glibc upgrade like this: - binaryname: relocation error: binaryname: symbol __guard, version GLIBC_2.3.2 not defined in file libc.so.6 with link time reference - I'm actually surprised how well my machines doing despite this problem.
For those who have the same problem, you can search for affected binaries using this command: - scanelf -qRs __guard /bin /lib /sbin /usr/bin /usr/lib /usr/sbin /opt /var/www/ - - equery belongs path/binary - command can be used to query for which package the binary belongs to. Can somebody update me on the nature of the problem? Is it an intended movement to drop __guard? I know, that it's obsolete. I would suggest to communicate this in an enews or whatever for all hardened users. Or I may be the only one, who rolls the system without regular world recompiles? Regards: Dwokfur -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057
