Comment 1 for bug 21705

On Jul 10, 2005, at 10:57 AM, Michael Shields wrote:

> However, this leaves a
> screensaver running on the old display, now hidden but likely
> consuming
> a significant amount of CPU.

Do you have evidence that this CPU usage is a problem? Because it
shouldn't be:
http://www.jwz.org/xscreensaver/faq.html#suspend

> It would be helpful if starting a new
> session also set the old one to a blank screen instead of a graphics
> hack, as if "xscreensaver-command -throttle" had been run.

Not a bad idea, I suppose, but the more general solution would be to
throttle while (and only while) the VT that the X server is running
on is not the selected one. You want the screen saver to un-throttle
when the user switches back.

However, I don't know how to tell A) which VT X is on; B) whether it
is the front; or C) when it changes.

--
Jamie Zawinski <email address hidden> http://www.jwz.org/
                     <email address hidden> http://www.dnalounge.com/
                                          http://jwz.livejournal.com/