3 ms·
>Half the software installers will tell you to restart when they're finished even though it's not necessary anymore Methinks you either don't know what is "nec
by warrenm 4y ago
>Half the software installers will tell you to restart when they're finished even though it's not necessary anymore
Methinks you either don't know what is "necessary", assume you know more than the developers of said software as to what is "necessary", or that you know better than OS vendors what is "necessary"
Rebooting is simple, fast, and basically pain-free 99.99% of the time
It clears memory, hung processes, file handles, and a host of other things - any (or all) of which could interact poorly with whatever software you're installing/upgrading may rely on
If an installer wants a reboot, I fully expect the software to likely not work 100% correctly until said reboot has completed
- viraptor 4y ago> Rebooting is simple, fast, and basically pain-free 99.99% of the time That's an end user view. For a server used by many employees, rebooting is disruptive, has to be scheduled out of hours, and requires extra testing afterwards. > It clears memory, hung processes, file handles, and a host of other things So does restarting a given process / service. (unless we're in the "your system is broken anyway" territory) Basically if the app is not modifying GPO, there's a tiny number of reasons to restart.
- warrenm 4y ago>That's an end user view. For a server used by many employees, rebooting is disruptive, has to be scheduled out of hours, and requires extra testing afterwards. Nope, it's a server and datacenter management view Been doing this for close to a quarter century across all kinds of platforms When the vendor says to restart, it's the Right Thing™ to do (whether you like it or not)