Best reason I can think of is application feature deprecation.
If an update contains changes to the default configuration file then the
file will normally be installed with the '.rpmnew' extension.
If an application decides to deprecate and phase out options which you
actually use in the current configuration then the automatic update will
invalidate your configuration and the service will not start.
This would cause downtime for your servers. In the case of some services
e.g. ssh, it could be catastrophic, requiring you to physically visit the
servers, would could incur a cost to you.
If you're OK with that, then you're not really in a high-availability
production environment and you can use the automatic update daemon if you
wish.
On Tue, January 17, 2012 17:30, P J wrote:
> I've read that it's not recommended to automatically apply updates via
> yum-updated on production servers, but I keep encountering servers that
> have this enabled.
>
> Are any of you doing automatic yum updates on production servers in CentOS
> 5 via yum-updatesd? Have you experienced any negative side effects?
>
> The only thing I can think of is if say a client had a custom version of
> PHP installed that was not properly excluded in yum and then it was over
> written.
> Unless I'm missing something else that could go horribly wrong.
>
> Any feedback is appreciated. (if this question has already been asked my
> apologies, searching the archive didn't find what I was looking for)
>
> Thanks,
>
> -PJ
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
