Re: shutdown from gnome logout dialog
On Sun, Oct 19, 2003 at 12:37:00AM +0200, Jarno Gassenbauer wrote:
> > >
> > > (Well, theoretically he could outsmart the lockup by hitting cancel
> > > and fireing up the logout dialog again, getting 15 more clicks)
> >
> > You should not really hang in the connection. I'd just initiate a new
> > connection and do authentication on every action. It really doesn't take
> > all that long. So every time the user clicks, open connection, auth,
> > do the command, close. That way you're not hogging the connection
> > anyway.
>
> I went for the persistent connection because I had another possible
> feature in mind: Multiuser spying!!!
>
> The logout dialog could have an entry telling you how many other users
> currently are logged in (or easier to code: how many other sessions are
> open). To have it updated in real time you need a persistent connection,
> or GDM had to connect to gnome-session. Or you have to do polling - but
> polling is even more evil than connecting to gnome-session.
That seems nice, but assuredly GDM would know about this (except for the
console sessions, that is). Why not do it like that :
You press the logout button.
Gnome-session or whatever asks GDM if there are other folk connected.
The response get printed in the dialog.
Second step, continue as usual.
Another idea would be to have GDM ignore shutdown/reboot requests if
there is more than 1 active session, but again, this doesn't count
remote login and console sessions.
> > > I agree to Jeff, but I'd maintain the patch until it becomes official.
> > > Well, at most for 10 years or so...
> >
> > Don't worry, it doesn't take that long to commit to cvs :)
>
> I know that you're fast :-) I just worried that it might never
> get official.
Well, once an official better solution is found, you remove the patch.
Friendly,
Sven Luther
Reply to: