On Jun 16, Graham Murray <graham@barnowl.demon.co.uk> wrote:

Would it not be a good idea, from a security point of view, for YAST2 to restart dæmons after it has updated them? It should at least give out a warning. On production systems the time between installing and restarting an update should be chosen by the admin and not the update tool. Some updates also cause configuration files to change, which would break the service upon restart. If the old version is still running, the admin can configure the new version meanwhile and restart later. Note that my tool, Fast OnlineUpdate for SuSE (http://fou4s.gaugusch.at) was designed with above reasons in mind. It is a replacement for YaST OnlineUpdate.

regards, Markus Gaugusch -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus@gaugusch.at X Against HTML Mail / \

On Jun 16, Graham Murray <graham@barnowl.demon.co.uk> wrote:

Would it not be a good idea, from a security point of view, for YAST2 to restart dæmons after it has updated them? It should at least give out a warning. On production systems the time between installing and restarting an update should be chosen by the admin and not the update tool. Some updates also cause configuration files to change, which would break the service upon restart. If the old version is still running, the admin can configure the new version meanwhile and restart later. Note that my tool, Fast OnlineUpdate for SuSE (http://fou4s.gaugusch.at) was designed with above reasons in mind. It is a replacement for YaST OnlineUpdate.

regards, Markus Gaugusch -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus@gaugusch.at X Against HTML Mail / \