yum update

[Bill Davidsen]

Gene Poole wrote:
> I started using yum to update my systems as-soon-as 'up2date' was no longer
> supported.  So, I have friends and people I work with asking me for a 'rule
> of thumb', which I don't know.  So, I'm asking the member of this list:
> 
>    What is the 'rule of thumb' for re-booting after the completion of the
>    'yum -y update' command? How do you know if you should re-boot - if
>    there is a kernel update? Should you reboot based upon what key
>    components have been updated?  How do you know what's been updated if
>    you schedule it to run at 2 AM?  Do you ever have to re-boot?
> 
> I don't have a answer to these questions, do you?
> 
No, I run check-update overnight and make a decision based on that, but 
it would nice if RPMs requiring reboot included /etc.need_reboot, and a 
script like /bin/reboot_if_needed you could run later.

I always check what's going to upgrade before I do it, I am not a 
trusting person. I also run the upgrade command with the names of the 
packages rather than just letting it do anything it wants.

For ease of having multiple machines I keep the RPMs and put them in a 
local repository, and I *do* just upgrade against that one, because I 
have tested the contents on at least one machine before distributing 
them. You can use 'localupgrade' to do this with NFS or even a CD if 
running a repository is a problem, works equally well.

-- 
Bill Davidsen <davidsen at tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot