On 2017-03-22T14:15:24, Thorsten Kukuk
However, both approaches are unsuitable for small updates IMO. On a traditional server it would be crazy to require a reboot just to apply e.g. a security update on apache or even systemd when both services can handle inline replacement just fine. And your apache case is the case, why big customers want to have transactional updates: for them it is not acceptable, that the web server is restarted during an update and maybe the transaction with the customer will fail because of that. They prefer to have scheduled reboots for this.
Any customer that runs more than one server as in the above will have some sort of HA/Load Balancing setup where they quiesce one at a time, update it, and bring it back online. Whether that includes a reboot or not is basically irrelevant - of course faster updates are always good, but the operational impact is low. I still really like transactional updates because then the system is always consistent, which is just nice, and it does have the potential of reducing the brief restart cycle. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org