On Tue, 2018-05-22 at 23:00 +0800, Ed Greshko wrote:
So, those processes may potentially keep copies of libraries that have been updated and (guessing) clashes happen with new processes with new libraries.
Yes, I'm aware of that. However 'tracer' supposed to detect this, either when called from the Shell or via the dnf plug-in. That's why it's telling me to restart the session.
I seriously doubt that tracer will be able to detect that some processes may survive a log-outt/log-in event.
Naturally not, but it should (and AFAIK does) detect libraries being updated and recommend that processes using them be restarted.
Do you run tracer again after logging in again?
I sometimes run it from a root console while the user session is logged out, and make sure nothing out of date is still hanging around. This doesn't appear to correlate with the problem, but I haven't been systematic enough about it to be sure.
Therefore, I don't logout/login after updates. If anything, I reboot. In my case a reboot takes about 12 seconds so I'm not bothered by it.
It's fast here too, but I usually have a VM running that I may not want to forcibly reboot.
There is always something, isn't there?
Yes, Murphy had something to say about that ...
poc