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:
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?