On Tue, Sep 29, 2009 at 7:23 PM, Seth Vidal <span dir="ltr">&lt;<a href="mailto:skvidal@fedoraproject.org">skvidal@fedoraproject.org</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><br></div></div>
And I think what Bill is saying is that a lot of users will not want to logout. They will want to just restart the app in question, if they are told which apps are impacted.<br></blockquote><div><br></div><div>This is what I meant in saying it&#39;s case by case, not something where one policy applies to all software.  If you just updated Firefox, then yes, we can and should have a system which knows how to restart just that application.</div>
<div><br></div><div>The discussion started about infrastructure bits, like:</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I don&#39;t expect to have to reboot just b/c of an issue in the sound server.<br></blockquote><div><br></div><div>Not reboot for this one but relogin.  Well, you can choose not to of course, but the point of an update is to actually update what&#39;s running on people&#39;s computers.  If the system doesn&#39;t reliably get us there it&#39;s not working..</div>
<div><br></div><div><br></div></div>