Hi Jimmy
It's all in the CAM script. Here's how I've done it in the past. The
benefits are that your screensaver and powersave mode will kick in, and
also that your thin clients won't be sitting at the Terminal Server
login screen (which can be a problem in its own right - see
http://groups.google.com/group/microsoft.public.windows.terminal_services/browse_thread/thread/e0bc0f31971104e0/fd0f4c0ad615fd7d
).
1. At the top of the CAM script, put in something like:
xset s on s blank s 300
This will set up the Sun Ray to automatically go into power saving mode
after 300 seconds of idle time (5 minutes).
2. Now just before your script runs uttsc, put in a line that runs this
"pause" program. It's basically a fake screensaver that blocks the
script until there is keyboard or mouse movement.
You'll need to compile it: the source is at:
http://tomshaw.id.au/errata/pause.c and instructions for compiling are
at the top of the file. It's basically a very small X application that
"fakes" a screen saver by drawing a large black rectangle and then exits
as soon as it detects mouse or keyboard activity. I've only tested it on
Solaris (SPARC and x86).
Hope this helps
Tom
Jimmy Fox wrote:
I'm sure this has been discussed but I have no more ideas on how to search for
it.
I'm calling uttsc via CAM mode as a critical app. Everything is perfect except
for those terminals that have smartcards inserted and no one there to login.
The login screen remains up indefinitely. Is there a way to make the
screen-saver (xset +dpms -s blank) run after the Windows session login times
out then loop back to the uttsc call after the user interrupts the screen-saver?
Thanks,
Jimmy
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
