Hello,
I want o run my desktop 24x7, but with large periods of inactivity. Thus, I have configured PM in my KDE settings (since the relevant Yast module is not implemented). The desktop is used by 3 people, so, I don’t want to do either of the following:
[ul]
[li]Copy the PM configuration from User A to Users B, C etc. This option, of course, creates more questions:[/li][LIST]
[li] Which file should I copy?[/li][li]How do I replicate this setting for each new user created on my desktop?[/li][/ul]
[li]Create a new system wide PM policy that will be forced to all users by default.[/li][/LIST]
I guess that if I copy the file in /etc/kde4/share/config/ it will be available globally, but I have to do it a clever way (soft link, maybe?), so I will not have a bunch of .rpm{new,old} files.
Thank you for your answer. It’s not working on my case, I believe. The issue is that I cannot make the desktop to actually go to sleep/hibernate when more than one users are logged in. Hmm.
And, which is the most important, even when I have only one user, when I hibernate the PC, it automatically starts again! So, I have this cycle:
Hibername–>“power off”…>auto power on!!!–>unbootable system!
It could be a hardware(UEFI/BIOS) issue, but the fact that the system is unbootable worries me a lot. It’s not normal.
Please be aware that, “sleep” and “hibernate” only make sense for systems with at most one human user using the machine (it sometimes makes sense for a remote stand-alone machines to autonomously put themselves into “sleep” or “hibernate” states but, please be aware that such machines have hardware which allows that an external event event can “wake-them-up”).
It could be that there’s an event occurring which brings the machine out of the standby or hibernate state: check the BIOS Advanced Power Management (APM) settings for things like:
Power on from S5 by PME (Power Management Event);
Power on from S5 by Ring (if there’s a modem connected, when someone places a telephone call to the modem’s telephone number the machine “wakes-up”).
Power on by PS/2 keyboard;
Power on from S5 by RTC (real time clock) alarm.
[HR][/HR]Bottom line: it’s possibly not very productive to attempt to save more power than that which current Linux systems already achieve: openSUSE is “green”, really . . . In earlier versions there were things which attempted to save power but, with 13.1 I gave up on doing anything – the power saving “out-of-the-box” is so good that hours of effort attempting to “improve things” doesn’t really bring any significant results . . .
In this case as it is KDE4, it needs to be placed in “/etc/skel/kde4/config/” though.
Files in /etc/skel/ will not be made available for all users though. They are only copied to a user’s home directory when you create a new user account.
Or you can indeed put config files to /etc/kde4/share/config/. Those are used as default then for all users (even existing ones), as long as they are not overridden by the user (in ~/.kde4).
And no, you don’t have to fear that that will create a bunch of .rpm{new,old} files.
Normally this needs the root password.
You can allow it in the polkit config though if you really want to. Add the following line to /etc/polkit-default-privs.local: