| Summary: | systemd autosuspends even in presence of active sessions | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Chris Denice <eatdirt> |
| Component: | RPM Packages | Assignee: | Base system maintainers <basesystem> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | systemd-241-1.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Chris Denice
2019-03-05 11:38:14 CET
Summary:
systemd autosuspend even in presence of active sessions =>
systemd autosuspends even in presence of active sessions
Marja Van Waes
2019-03-05 12:05:06 CET
CC:
(none) =>
marja11 |
Description of problem: In /etc/logind.conf, I have my server configured as: IdleAction=suspend IdleActionSec=10min Such that, if users are disconnected, the server automatically suspend-to-ram. It used to work fine, but with the new systemd, the system suspend even when users are connected by ssh and active: For instance, while compiling something, after 10mn the system suspends. Remote sessions are there, loginctl returns them as loginctl SESSION UID USER SEAT TTY c12 1002 eatdirt pts/1 c13 1002 eatdirt pts/2 c7 1002 eatdirt pts/0 3 sessions listed. But still, systemd puts the machine in suspend. I don't see any new options explaining this behaviour, so I suspect it is a bug. Notice that the machine is running in runlevel 3. Cheers, Chris.