"Neal A. Lucier" <[EMAIL PROTECTED]> wrote: > In both CDE's and GNOME's screensaver there is a distinction > between blanking a screen and locking a screen; however, NSCM > doesn't seem to be aware of these differences and detaches the > session from the DTU if either of the screensaver modes are entered.
NSCM is supposed to detach the session only when the screensaver locks the screen. Specifically NSCM detaches the session when the screensaver invokes PAM, which indicates that the user will need to reauthenticate in order to regain access to the desktop. If the screensaver only blanks the screen or puts up some screensaver eye candy then NSCM shouldn't even be aware that that's happening. > I (and my more vocal users) believe that the session should stay > attached if the screen is only blanked, but should become detached > if the screen becomes locked. Yes, absolutely. > Is there any way to configure this behavior? No, it's just always supposed to always work the way you want it to work. Do nothing when a saver starts, detach the session on lock. Are you sure that you have your screensaver configured to blank some time ahead of when it's configured to lock? Can you verify outside of NSCM that the screensaver really does blank ahead of locking, say in a smartcard session or on the console or in a remote X login? Can you capture a 'truss -f -u""' of a screenlock process at the time it detaches a session as a side effect of blanking the screen? That'll show you whether it's calling PAM at that time. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
