home-manager systemd user units aren't auto-started?

nix-community / impermanence

Modules to help you handle persistent state on systems with ephemeral root storage [maintainer=@talyz]

MIT License

1.09k stars 80 forks source link

home-manager systemd user units aren't auto-started? #45

Open colemickens opened 2 years ago

colemickens commented 2 years ago

I'm on a new box setting up impermanence for the first time.

I'm having to move some dirs out of the way to get home-manager-cole.service to activate properly.

However, it did start, but the actual bind mount units are all dead/inactive. I've had to start them myself?

talyz commented 2 years ago

Did you try to switch to the new configuration without rebooting? This would increase the likelihood of things being in the way. Also, I don't think recent versions of home-manager does the necessary user service activation on switch - I think you have to set systemd.user.startServices = true for it to work.

colemickens commented 2 years ago

hmm.

dschrempf commented 1 year ago

Hi, I just wanted to say that I also needed the systemd.user.startServices = true setting on my headless server to get the Home Manager services started without a proper user login.