Jeremy Y Uejio wrote:
Bob,
On 08/13/09 09:11 PM, Bob Doolittle wrote:
> gnome-screensaver-command. So on such systems we launch a utaction
> similarly to utxlock but which invokes gnome-screensaver-command to
> unlock the session on a connect.
I didn't know that you can unlock the xscreensaver programatically.
How is that done?
It can be deactivated using gnome-screensaver-command --deactivate.
Thanks
P.S.M.Swamiji
Note: These are my personal opinions, nothing to do with my employer
jeremy
On 08/13/09 09:11 PM, Bob Doolittle wrote:
There's a utaction launched from
/usr/dt/config/Xsession.d/0100.SUNWut that runs in the background of
every session not protected by loginGUI (e.g. NSCM or RHA). When a
session disconnects, it calls utxlock to invoke the screen locker, so
every detached session is locked and can't be accessed without
authentication.
pam_sunray.so, with the syncondisplay option, will detach the session
when locked (not by calling utdetach, but by invoking a callback
directly on utauthd port 7010). On reconnect, it calls back to
utauthd to see if an out-of-session authentication has just been
performed (e.g. RHA or NSCM) and if so it immediately causes the
screensaver to unlock (returns PAM_SUCCESS as 'sufficient' in pam.conf).
There's also a hack on systems that use gnome-screensaver called
utxunlock. The problem is that gnome-screensaver doesn't call
pam_authenticate immediately when the screen is locked, so
pam_sunray:pam_sm_authenticate() doesn't get invoked to unlock the
session when it reconnects. The good news is that it's
multi-threaded, so even when blocked in pam_authenticate it still
processes calls from gnome-screensaver-command. So on such systems we
launch a utaction similarly to utxlock but which invokes
gnome-screensaver-command to unlock the session on a connect.
Unfortunately there's no way to disconnect on a lock for such
systems, which is why we recommend people use Shift-Pause/utdetach
instead.
-Bob
Juarez, Marc wrote:
Hello,
I have been searching through the mail list archives and reading the
Sun docs on wikis.sun.com (wtg sun! better than pdf format imho) for
additional information on Sunray screen locking and session
detaching. I am having tough time finding information on how this
process works. I know that there are several pam modules that SRSS
uses to perform actions based on xscreensaver and dtscreen. When and
what process calls utdetach? Is it when the screensaver for the
window manager engages/locks the screen? What role does utxlock
have in this process? I started my search due to a display server
requirement to automatically utdetach a session after a certain time
interval that cannot be overridden by a user configurable variable
on the server. During my research I located the system wide dtscreen
and xscreensaver configurations files located in...
/usr/openwin/lib/app-defaults/XScreenSaver
/usr/dt/app-defaults/C/Dtscreen
I thought that these configuration files would help my satisfy my
requirement but after reading a few man pages both of these files
can be superseded by a configuration file in a users home directory.
Any assistance anyone can provide would be greatly appreciated.
Thank You
-Marc Juarez
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
