Solaris 2.5.1 - powerd problem

by Duggan Lorca » Thu, 10 Jul 1997 04:00:00

Why won't the powerd put the system in standby mode if I have the CDE
screen lock running. I've put entries for loadaverage up to 100% and
diskreads to 100 for an idle period of 15 minutes,but to no avail.
Anyway, running top I see that the CDE screen lock is making negligable
demands on the CPU.

Any ideas welcome

Lorcan

Top

1. xlock in Solaris 7 doesn't work with powerd?

I have observed that after upgrading to Solaris 7, the powerd running
on none of the desktops here puts the monitor in energy saving mode
if the user locks the display using xlock.

Before, when all our desktops were running Solaris 2.5.1, after 30 mins
of idle time, the powerd would kick in and put the monitor in energy
saving mode regardless whether xlock was running or not. This is a much
preferable behavor to us.

I did the following experiment:

1) xset s 5, so that after five seconds of idle time, the X screensaver would
kick in. It did. But this was without xlock. Powerd kicked in soon
afterwards.

2) invoke xlock as xlock +enablesaver. After five seconds, the screen saver
didn't kick in at all. Thus the powerd wouldn't put the monitor in
energy saving mode.

Even the man page of xlock claims that +enablesaver would enable the X
screensaver, looks like it doesn't. So, is this a bug or a feature?

In any case, has anyone able to "restore" the more desirable behavor
when using xlock? If so, I would love to know how you got it working.

Regards,

Chin Fang

2. NEW PRODUCT : 3 Linux CD's and a....

3. powerd on Solaris 8

4. Please ignore newbie Missing RGB_DB question

5. powerd 2.0 problem

6. SIMS Implementation

7. Powerd Problem

8. Netscape lock

9. Powerd client for other systems?