> Am 27.01.2017 um 17:27 schrieb m.roth at 5-cent.us: > > Johnny Hughes wrote: >> On 01/27/2017 09:19 AM, Jon LaBadie wrote: >>> With a large update to be made, eg. the 900 package >>> one I questioned yesterday, are there any suggestions >>> to avoid possible complications? >>> >>> Two examples, I'd like to know of others too: >>> >>> I'm not running the most recently installed kernel, >>> I assume I should reboot to that. >>> >>> I normally have a graphical environment running. >>> Would it be better to: a) shutdown X and update >>> from a straight CLI environment b) logout from >>> the GUI and update from a vt CLI c) update from >>> a GUI login as root or d) doesn't matter, do as >>> normal -- from an ssh login, "sudo yum update"? >> >> It is certainly better to upgrade with less things running as a general >> practice. >> >> One should never update from a Remote X type connection via VNC or NX, >> etc. >> >> The absolute safest way to upgrade would be to do so via the console and >> a keyboard on the actual machine if there is some issue with sshd, etc. >> >> But generally, this upgrade should be OK via ssh, etc. >> > On our about 200 workstations and servers, we just ssh in and run the yum > update. Workstations... we co-ordinate with the user, and yes, it's better > if they log off. Still, ssh in has always been fine (unless you have to > worry about the video, such as NVidia or AMD proprietary video drivers). > In such scenario (xxx packages to update) I normally split the update command into # yum clean all # yum update glibc* rpm* yum* # yum update # reboot -- LF