3 ms·
>What I expect it also means is that you'll get inconsistencies when doing inter-process communication, since they'll be using different libraries with potentia
by tzahola 9y ago
>What I expect it also means is that you'll get inconsistencies when doing inter-process communication, since they'll be using different libraries with potential mismatches.
That's why you should restart those programs that were using the library. You can find this out via `lsof`.
- mehrdadn 9y agoReally? Somehow procure a list of all libraries that were updated in a system update, go through each one, find out which program was using it, and kill that program? Every single time I update? You can't be serious.
- beagle3 9y agoApt does this automatically for you on uphrade
- jlgaddis 9y ago"checkrestart" also exists (on some distributions) for exactly this same purpose.
- avar 9y agoWhat you're describing is trivially done on any *nix system with a mature package manager, if it isn't doing this already: 1. Do the upgrade, this changes the files. 2. You have a log of what packages got upgraded. 3. Run the package system's introspection commands to see what files belonged to that package before & after 4. Run the package system's introspection commands to see what reverse depends on those packages, or use the lsof trick mentioned upthread. 5. For each of those things restart any running instance of the application / daemon. Even if something didn't implement this already (most mature systems to) this is at most a rather trivial 30 line shellscript.