You'd be amazed at what you can install without rebooting. True, most MS software tries to reboot the machine for you because heck, that's just easier than doing it the right way.
After installing something, if I really don't want to reboot, I just look in the reg at the pendingfilerename ops and see what files it was trying to replace that were in use. Then I stop the services that were using those files, rename the files myself to copy the new ones over, and restart the service... Voila. Except for certain critical components, this will work all the time. Probably 90% of all the installs that ask you to reboot can be solved without a reboot if you want. The other 10%, well, what can I say. You can't install a new kernel without a reboot either. :) I just chalk the MS "reboot always" to an old philosophy, laziness... Whatever. There have been definite improvements over the past few years with succeeding OS's although I still think most install programs are reboot happy without need. > >I second that sentiment. I've had Win servers that ran and > ran and ran > >for ages it seemed. > The *only* way to pull that off is to totally ignore security > updates (and the subsequent reboot). No thanks. :) ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
