https://bugzilla.novell.com/show_bug.cgi?id=804454 https://bugzilla.novell.com/show_bug.cgi?id=804454#c14 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|jsuchome@suse.com |fehr@suse.com --- Comment #14 from Thomas Fehr <fehr@suse.com> 2013-04-18 12:34:51 UTC ---
Do you propose any deeper change in autoYaST logic based on current behavior?
I had a new idea this morning and am experimenting with it. While autoyast cannot know which services need to be restarted due to configuration changes, it could simply restart all services that are in running state. This should solve all potential problems with changed config files for services already running. No modules beside autoyast would be affected and so far I see no disadvantages (the system is not (yet) in a usable state at this time anyway), but I did not try it yet.
For now, I'd just close it with the offical 'use final_reboot' advice.
I just reassigned it to me. I hope I will have something which Joschi Brauchle could test either today or early next week. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.