On Fri, Jan 26, 2001 at 06:36:40AM -0900, James wrote:
> 
> I just read through this thread, but you may find that xscreensaver is the
> cause.  I run Seti@Home, so pay attention to what is using how much of the
> processor.  Normally, with the computer awake, Seti@Home gets 96-99% of the
> processor.  With the X screen saver running and checking top from another
> console, I would see that Seti@Home was getting 46-49% of the CPU while
> xscreensaver took up the rest (and of course a little for top, etc.).
> 
> I killed the xscreensaver and just use power management to turn off the
> monitor when idle - however that means I can't lock my screen either.

That seems to have been the problem.  Must be something going on in the
xscreensaver server process...  Anyway, I really didn't need those fancy
displays anyways, so I just turned it off and let the X server handle the
screen saving.  If I need it locked, I use xlock.

Thanks for the help!!

-Michael

-- 
No, my friend, the way to have good and safe government, is not to trust it
all to one, but to divide it among the many, distributing to every one exactly
the functions he is competent to.  It is by dividing and subdividing these
republics from the national one down through all its subordinations, until it
ends in the administration of every man's farm by himself; by placing under
every one what his own eye may superintend, that all will be done for the
best.
                -- Thomas Jefferson, to Joseph Cabell, 1816



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to