On Fri, 2008-10-03 at 23:23 +0100, Karanbir Singh wrote: > Vandaman wrote: > >>From the notes on the "bug" you would have to have 4.5/os/$basearch/ > > instead of $releasever/os/$basearch/ to get the "bug". > > And you assume that since he is seeing similar effects, he must also > have done the exact same thing ? > > > Also yum update > > or upgrade should not break anything unless you have packages from > > elsewhere and murked about with the configs. > Forget that bug, it was a totally differnet machine and i don't want this mixed up here, may be it was my fault, it doesn't matter. > > I have looked on the last month's list and not seen :- > > > > - people whose machines took weeks to autoupdate. > > - people whose production machines were broken by 4.6 to 4.7 > > > > Clearly Lutz's situation is unique and he has not told us the whole story. > You don't wanna hear the whole story, i can tell you... :) >From my point of view, i wouldn't let do a productive machine such an update unattended, that's why i switched it off (as i already said, i didn't know, it was turned on). Neither yum nor I can presume the impact. Not that i blame yum for it, i don't expect it can foresee all complexities of any installed software. i'd like to monitor every update in a downtime window (for productive machines!), just to be save i don't run into trouble, when the box is needed. I also wouldn't do any "dist-upgrade" in debian or install service Packs on windows (forgive me _that_ analogy...) without watching it. For my own curiosity, i'd like to know the reason, why it took almost 3 weeks before the updates hit the machine. The Base Repository gets its mirrorlist from "mirrorlist.centos.org". I can post it, if you want. What might be interesting is the fact, that there is also the "dag" repository (http://dag.wieers.com) enabled, where the nagios-nrpe package comes from. For the dhcrelay issue: The update brought dhcp.x86_64 7:3.0.1-62.EL4 and in the messages i have an entry with succeeded TERM signal Oct 2 04:14:02 trainer dhcrelay: dhcrelay -TERM succeeded shouldn't it get -HUP Signal or completely restarted? Regards Lutz