http://bugzilla.suse.com/show_bug.cgi?id=1159877 http://bugzilla.suse.com/show_bug.cgi?id=1159877#c12 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jsrain@suse.com) | --- Comment #12 from Jiri Srain <jsrain@suse.com> --- (In reply to Josef Reidinger from comment #8)

jiri - do you remember reasoning for that timeout? And what is the way to initiate such reevaluate?

I guess that the current behavior is with SUSE longer than I am. I can see the value of the time-out that it allows me to stop the process at the end and grab the logs if needed (for reporting another bug). Removing the time-out and rebooting imeedately - I don't see any use case except saving those 10 seconds. If we want to do any change, I suggest not to add it to the UI, but stick with the command-line; I don't expect current behavior to be any issue for the majority of users, but rather something for a specific customers. BTW: IIRC, AutoYaST has its means to control what should happen after installation - for unattended mass deployments. -- You are receiving this mail because: You are on the CC list for the bug.