Tom Shaw wrote:
In Solaris at least you need to use xset instead of xscreensaver:
/usr/openwin/bin/xset s on s blank s 300
(blank after 300 seconds - this may not be the exact syntax but it should get
you started)
If you want to turn this on for every user, put it in a script in
/etc/dt/config/Xsession.d/
This should *not* be required, and if this fixes
the issue, there's a bug either in xscreensaver or
SRSS.
We've heard scattered reports on this, but so far
haven't identified the common
circumstances/environment. Many people are using
xscreensaver with S10 and SRSS 3.1 with latest
patches and monitors are power-saving just fine.
Others have issues as you describe, with similar
monitors.
Screen savers, such as xscreensaver, are supposed
to set the X server parameters for blanking
directly. So it would seem that in some
circumstances either those parameters are not
being set properly, or the X server or SRSS is not
handling them properly, or the administrator isn't
configuring xscreensaver properly (no offense
folks, but admins make mistakes too :-).
If you're certain that xscreensaver is configured
properly, and you're certain that you're seeing
this problem (screen is blanking, but monitor is
not ever going into power-save mode), can you run
"xset q" and send the output to this list?
-Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
