By bhlackey on Apr 12, 2006
Some Sun Ray deployments require having data on the screen at all times. The DTUs are being used for monitoring the current state of something or displaying reference data.
In these scenarios it is important that the screens are always active, and usually there is no mouse or keyboard to wake them from power saving/screen saver mode.
When used in CAM mode to connect to Windows, there are two screen blanks that can happen, one through the X server on the Sun Ray server and one with the Windows screensaver. The Windows screensaver is easily fixed with right-click on background and choose "None" on the sceensaver tab.
Since in CAM mode there is no GUI to configure the X screensaver, the xset command with the appropriate entries needs to be run after the X Session is started.
The solution is to add a line to the beginning of your CAM application script to execute the "xset" command before launching the interop client. (SRCW, SGD, etc.)
The correct command is:
xset -dpms -fbpm s off
After adding this line to your CAM script, any new sessions will get the change but old sessions will need to be reset to receive the change.
This currently is an all or nothing fix. It will turn off the sceensaving feature for all users at once. You could configure the Windows screensaver to blank the screen after a period of time for individual users, but this will not let the DTU go into low power mode.
There is the possibility of using a script similar to the Folllow-me-printing script to enable/disable screen blanking on a per-DTU basis if necessary.