|
Here's my message I tried sending on 16 October 2017 18:13 UTC, now 17 October 2017 19:40 UTC and I haven't seen it posted yet... I noticed the response from Don Armstrong saying it may need to be whitelisted. Hope this one goes through! Sorry I'm causing
so much overhead here folks.
On 10/16/2017 11:13 AM, Lucky0106 wrote:
My emails to this list are delayed by about 24 hours (am I the only one?) but I think I may have solved my issue with systemd-logind, thanks to the helpful command posted earlier
by Mr. Biebl.
After running the command, I saw a message that grabbed my attention; "suspend.target is masked". Jumping back on to the search engines, I come across this
<http://forums.debian.net/viewtopic.php?f=5&t=129356> topic almost immediately (somehow my searching before completely missed it?). In the topic, the user was experiencing nearly the exact same issue. They checked /etc/systemd/login.conf and set the following
options:
HandlePowerKey=poweroff
HandleLidSwitch=ignore
IdleAction=ignore
IdleActionSec=30min
Going to the /etc/systemd folder however, I see that there is no login.conf file - only a login.conf.bak file, which I must have been editing before since a couple of the lines were already commented out. I mv'ed the file back to login.conf, made sure
the above lines were enabled, and rebooted the machine. No more excessive CPU usage!
I think this raises a few questions;
- Why was this absurd CPU usage occurring in the first place,
- In the comments at the top of the file, it seems implied that the file should be regenerated if it does not exist. Then why wasn't the file being regenerated since I had moved it? What was logind using as configuration instead?
Does anyone think this deserves a bug report or am I misunderstanding something here?
Glen
|