The only time I had remote updates not work, is when either : a)Someone leaves a floppy in the machine and it tries to boot of it when I reboot.... b)Someone leaves the keyboard disconnected or something resting on the keyboard. I've had very few genuine issues where a machine dies after a solid yumming session... P. Scott Silva wrote: > Sam Drinkard spake the following on 3/20/2006 7:39 AM: > >> My server has not yet been updated with all the goodies and is still a >> stock 4.2 installation. What is the consensus about remote updating? >> Would it be better if I were to physically be there and do it or are >> things stable enough that I could do it remotely and then reboot. It's >> kind of a PITA to have to go downtown to the C0-LO site, but can be done. >> >> >> Thanks.. >> >> Sam >> > A remote update works 99.99% of the time, but nothing is "infallible". You can > do the remote update, and run downtown only if it fails. You only need a > reboot if you get a new kernel, which you will probably get. The biggest > gotcha is if you are running something non-standard that an update might hose. > But if that is the case, you can always remotely fix it or try to go back. > > The risk of running without the updates can offset the risk of updating most > of the time. > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > >