On Thu, 2009-08-13 at 08:53 -0500, Les Mikesell wrote: > Geoff Galitz wrote: > >>> Can any one clarify this, is auto updating at all production servers > >>> recommended or not? > >>> need to know your opinion, how do you manage the update? > >>> > > > > > > I've worked on projects where backend configuration files changed in syntax > > or architecture between releases, which were released as updates... so I > > know for a fact updates can break a running system. > > On CentOS? Fedora does that all the time but _not_ having behavior-changing > updates in the long life of a major release is most of the point of 'enterprise' > distributions. It's probably not perfect - and I wouldn't do auto-updates on > production servers either but it should at least be very unusual for a CentOS > update to break anything. > I agree. However, my experience with CentOS requires me to state that updates modifying config files is rare, but NOT unknown. Precautions such as testing on non-production systems, should be taken, if only to deal with Murphy's Law. -- Ron Loftin reloftin at twcny.rr.com "God, root, what is difference ?" Piter from UserFriendly