3 ms·
Still, each individual process using an updated library needs to be restarted for the update to take effect. The way I see it, Linux does give you much more fl
by tsimionescu 7y ago
Still, each individual process using an updated library needs to be restarted for the update to take effect.
The way I see it, Linux does give you much more flexibility in how to deal with these restarts; and the ability to overwrite libraries on disk guarantees you don't get into the horrible Windows update-restart-update-restart cycles: you only ever require one restart at most.
However, there are also risks. For one, if you don't restart long-running processes which use updated shared libraries your system may be at risk; also, even if the update was not a vulnerability fix, it is technically possible for processes that communicate through a shared library to misbehave if they have different versions (one using the old library with an old data-structure for example).
This probably doesn't happen so much in Linux, where IPC is commonly done through text streams, but may be a much bigger problem on Windows if you update some COM library for example, reducing the usefullness of no-restart updates.