Re: Who is sending my Guix System to sleep?

[Ludovic Courtès]

Hello!

Konrad Hinsen <address@hidden> skribis:

> The only problem is that after 20 minutes, the virtual machine
> seems to freeze. I found the cause in /var/log/messages:
>
>     Sep 26 08:54:40 localhost NetworkManager[282]: <info>  [1569480880.2246] 
> manager: sleep: sleep requested (sleeping: no  enabled: yes)
>     Sep 26 08:54:40 localhost NetworkManager[282]: <info>  [1569480880.2247] 
> manager: NetworkManager state is now ASLEEP
>     Sep 26 08:54:40 localhost NetworkManager[282]: <info>  [1569480880.2248] 
> device (enp0s3): state change: activated -> deactivating (reason 'sleeping', 
> sys-iface-state: 'managed')
>     Sep 26 08:54:40 localhost NetworkManager[282]: <info>
>     [1569480880.2293] device (enp0s3): state change: deactivating ->
>     disconnected (reason 'sleeping', sys-iface-state: 'managed')
>
> Something requests NetworkManager to go to sleep, which is obviously not
> good for my ssh connection. But what?

I think elogind is the thing you’d want to configure to turn off
automatic standby when the machine is idle, presumably by changing the
‘idle-action’ field of <elogind-configuration>?

logind.conf(5) is not entirely clear, though:

--8<---------------cut here---------------start------------->8---
IdleAction=
    Configures the action to take when the system is idle. Takes one of 
"ignore",
    "poweroff", "reboot", "halt", "kexec", "suspend", "hibernate", 
"hybrid-sleep",
    "suspend-then-hibernate", and "lock". Defaults to "ignore".

    Note that this requires that user sessions correctly report the idle status 
to the
    system. The system will execute the action after all sessions report that 
they are
    idle, no idle inhibitor lock is active, and subsequently, the time 
configured with
    IdleActionSec= (see below) has expired.
--8<---------------cut here---------------end--------------->8---

HTH!

Ludo’.