3 ms·
Only rolling distros should be shipping mid-release cycle updates that break libc compatibility. It's not a normal thing for release-based distributions where
by PlutoIsAPlanet 3y ago
Only rolling distros should be shipping mid-release cycle updates that break libc compatibility.
It's not a normal thing for release-based distributions where userspace<>userspace compatibility is nearly assured during a release.
- jmetzmeier 3y agoCompatibility does not need to break to require a restart of a process. Linux does not have a mechanism that tells processes to reload their shared libraries when they are modified on disk. When a .so file is updated on disk, for example a minor update for a security vulnerability, all processes using that library need to be restarted to utilize that new update. If you're not restarting processes on these upgrades, you are not getting their benefits.This is why tools like dnf-tracer-plugin exist, but it's often just as easy to reboot, especially if you built your systems to be fault tolerant.