Describe the bug

When putting systemd.lorri.enable = true; in your system config, you would assume that the socket unit appears immediately after a system switch, but in fact it only does after reboot. Logging out and into the user account does not help.

To Reproduce

• Remove any lorri from your system
• If you had the service active, remove from your config and reboot
• Add lorri.service.enable = true; and switch your system (at least nixos 20.03)
• systemctl --user does not have any lorri service or socket
• reboot
• systemctl --user has the lorri.socket now

Expected behavior

The socket file should appear immediately after the NixOS system switch.

Additional context

Grepping through nixpkgs for systemd.user.sockets (and similar) only yields like three results, so it might be that starting a .socket unit for the user daemon is just not a common use-case and we’re in uncharted territory.

Possible solutions I can think of:

• Can we set up lorri as system service instead of user service? Would there be cons?
• Document that a reboot is necessary. That’s meh
• Fix the systemd.user config to update on switch. Probably hard, might even be impossible.

cc @curiousleo