Edward: On 08/12/09 22:24, Halton Huo wrote: > On Wed, 2009-08-12 at 17:18 +0800, Edward Shu wrote: >> What is "session migration" here? Does it mean the session can be >> migrated from >> one VT to another VT? With VT, will ConsoleKit be noticed the session >> switch? >> Session switch may automatically cause the keyboard and mouse migration >> between sessions. Currently in Solaris, graphics session will grab the >> mouse and keyboard input from the text session in the session switch. >> > Leave the session migration question for Brian.
The VT framework takes care of making sure that mouse and keyboard input is managed when VT switching takes place. Refer to PSARC 2006/591 and PSARC 2008/515. When you switch to another VT when you have an existing user session running, then the screenlock program is automatically launched so that the VT you just switched away from will be locked. If the user switches back to it, then they need to re-authenticate with the lockscreen program to get back into their session. If the user switches to a VT where there is not an existing user session running, then the user will be presented with the GDM login program. If the user tries to log into a user who already has a session running, then migration is done. GDM will do a chvt() call on the Xserver running the existing session. This switches the current active VT to where the user's session is running. In this case it will also unlock the screensaver since the user doesn't need to re-authenticate after logging in via the GDM greeter. Brian
