[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Single Page
Top Document: comp.unix.aix Frequently Asked Questions (Part 2 of 5)
Previous Document: 1.505: VT100 key bindings for aixterm
Next Document: 1.507: Where are the colors, available for an X session, listed.
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Single Page
Top Document: comp.unix.aix Frequently Asked Questions (Part 2 of 5)
Previous Document: 1.505: VT100 key bindings for aixterm
Next Document: 1.507: Where are the colors, available for an X session, listed.
1.506: Is there a screen saver that does not use excessive CPU?
Try using xlock with these options: xlock -mode life -count 1500 -nice 20 -root From: pranav@evolving.com (Pranav Vakil) Use mlock -hide to hide the background. You can also modify the mlock (/usr/local/tools/mlock) code to allow the standard X screen saver to take effect. The timeout value is originally set to 0 which means the screen saver is off. Modify this to be 120 (2 minutes) and set the interval time to be 60 (1 minute). Using these intervals, I have found that over a 24 hour period, it uses only .3 cpu minutes.
Top Document: comp.unix.aix Frequently Asked Questions (Part 2 of 5)
Previous Document: 1.505: VT100 key bindings for aixterm
Next Document: 1.507: Where are the colors, available for an X session, listed.
Part1 - Part2 - Part3 - Part4 - Part5 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
bofh@mail.teleweb.pt (Jose Pina Coelho)
Last Update October 22 2009 @ 05:22 AM