I have some laptops running F20/KDE which, among other purposes, are acting as gateways to a private network. Most of the time these laptops are unattended -- no one is logged into the console -- but the gateway function must continue to run so that remote users can reach the private network. So I need to prevent these laptops from going to sleep.
It appears that KDE's power management function applies to the user logged into the console. If a user is logged in, I can easily prevent sleep. But if the user logs out or the laptop is booted by a remote user, no power management seems to be active and they eventually go to sleep.
Is there a way to keep the power management function active even when no one is logged into the console?
Allegedly, on or about 01 August 2014, CLOSE Dave sent:
Is there a way to keep the power management function active even when no one is logged into the console?
Perhaps you can configure power management options for the kdm user (that which the KDM logon screen runs as)? Assuming that kdm works in a similar way as GDM does.
I asked:
Is there a way to keep the power management function active even when no one is logged into the console?
On 08/02/2014 08:19 AM, Tim wrote:
Perhaps you can configure power management options for the kdm user (that which the KDM logon screen runs as)? Assuming that kdm works in a similar way as GDM does.
So far as I can tell, there is no KDM user. Certainly there is no such user in /etc/passwd and no active process has such an owner. It appears that the login screen runs as root. In any case, KDE is not running until someone logs in. You can observe the KDE startup process after logging-in.
So, although I mentioned that the machine uses KDE, I doubt that is relevant. I'm just trying to get a laptop, plugged into mains power, never to go into a suspended state, whether or not someone is logged into its console. As the machine is on the network, it is possible for a remote user to cause a reboot. After that, even if the KDE power manager was running for a console user before the boot, it isn't running after the boot, so KDE's power management can't help at that time.
Perhaps I'm asking the wrong question or implying an answer that isn't helpful. Rather than my initial question, perhaps I should have asked,
Is there a way to prevent an unattended laptop from going into suspend even when no one is logged into the console?
On Fri, Aug 1, 2014 at 10:45 AM, CLOSE Dave Dave.Close@us.thalesgroup.com wrote:
I have some laptops running F20/KDE which, among other purposes, are acting as gateways to a private network. Most of the time these laptops are unattended -- no one is logged into the console -- but the gateway function must continue to run so that remote users can reach the private network. So I need to prevent these laptops from going to sleep.
It appears that KDE's power management function applies to the user logged into the console. If a user is logged in, I can easily prevent sleep. But if the user logs out or the laptop is booted by a remote user, no power management seems to be active and they eventually go to sleep.
What display manager are you using? `systemctl show display-manager.service -pId` will tell you.
KDM is the default display manager on the Fedora KDE spin, and KDM is ancient and crufty and doesn't even do power management, so I don't think you're using it?
I'm pretty sure you have to either be using GDM or lightdm to even have power management on the login screen, in which case switching to KDM (`yum install kdm && systemctl enable --force kdm.service`) would be an easy workaround.
-T.C.
T.C. Hollingsworth wrote:
What display manager are you using? `systemctl show display-manager.service -pId` will tell you.
# systemctl show display-manager.service -pId Id=kdm.service
KDM is the default display manager on the Fedora KDE spin, and KDM is ancient and crufty and doesn't even do power management, so I don't think you're using it?
I'm pretty sure you have to either be using GDM or lightdm to even have power management on the login screen, in which case switching to KDM (`yum install kdm && systemctl enable --force kdm.service`) would be an easy workaround.
Thanks for the reply. I interpret your comments to imply that, because I'm using KDM, the laptop should never go to sleep while at the login screen. Unfortunately, that is not my experience. If the laptop is closed, it goes to suspend within a few minutes. That is what I'm trying to prevent.
Allegedly, on or about 05 August 2014, CLOSE Dave sent:
If the laptop is closed, it goes to suspend within a few minutes.
As a side issue, you need to check that your laptop won't overheat if the lid is shut. Some of them have ventilation around the keyboard, and need it.
On Tue, Aug 5, 2014 at 9:46 AM, CLOSE Dave Dave.Close@us.thalesgroup.com wrote:
Thanks for the reply. I interpret your comments to imply that, because I'm using KDM, the laptop should never go to sleep while at the login screen. Unfortunately, that is not my experience. If the laptop is closed, it goes to suspend within a few minutes. That is what I'm trying to prevent.
Oh, this is probably systemd. I glossed over the word "laptops" in the beginning of your e-mail, sorry.
systemd (by default) doesn't put idle systems to sleep, but it does put closed laptops to sleep when no desktop power management system is active (e.g. when KDM is running).
Just set HandleLidSwitch=ignore in /etc/systemd/logind.conf to turn it off. See `man logind.conf` for more information.
-T.C.
T.C. Hollingsworth wrote:
systemd (by default) doesn't put idle systems to sleep, but it does put closed laptops to sleep when no desktop power management system is active (e.g. when KDM is running).
Just set HandleLidSwitch=ignore in /etc/systemd/logind.conf to turn it off. See `man logind.conf` for more information.
Thank you. That was precisely the information I needed.
-
CLOSE Dave -
T.C. Hollingsworth -
Tim