| 30 Apr 2025 |
 vaw | Do you have experimental-features = nix-command flakes in your ~/.config/nix/nix.conf? | 12:45:15 |
 Dreamgineer | Because home-manager failed to activate, ~/.config/nix/nix.conf disappeared completely | 12:45:46 |
| Dreamgineer | # modules/home/programs/nix.nix
{
nix.settings = {
experimental-features = [
"nix-command"
"flakes"
];
};
}
| 12:47:19 |
|  @_oftc___monty__:matrix.org joined the room. | 17:05:30 |
|  @regalk:regalk.dev joined the room. | 17:40:33 |
| @regalk:regalk.dev left the room. | 17:40:54 |
|  @skyesoss:matrix.org joined the room. | 19:53:34 |
| @_oftc___monty__:matrix.org left the room. | 21:37:25 |
| 1 May 2025 |
|  Leon joined the room. | 00:05:57 |
|  mbkqrqj joined the room. | 01:55:12 |
| @_oftc___monty__:matrix.org joined the room. | 15:57:02 |
|  musicmatze joined the room. | 17:10:49 |
| musicmatze | Hello home-manager users. I try to use home-manager to configure an instance of syncthing for a user camera. Unfortunately, the service only starts when I log in the machine with that user. Is there a way to always start that service? | 17:51:26 |
| vaw | The problem is that home-manager creates a systemd user service. The systemd user session only starts when a user logs in the first time after boot. I think you best choice would be to create a system service (maybe with nixos) and use the User parameter to run it as camera. | 17:56:18 |
| musicmatze | vaw: thanks for the fast reply. The problem is that it is not the only syncthing instance I want to start on that machine, hence the idea to configure it as user service - I will probably have another 2 or 3 instances of syncthing running on that device... | 18:00:27 |
| vaw | You might als try to set up a system service that logs in as the user to start the user session. I don't know how hacky that would end up being though. | 18:01:50 |
| vaw | * You might also try to set up a system service that logs in as the user to start the user session. I don't know how hacky that would end up being though. | 18:02:00 |
| musicmatze | Sounds very hacky, yes 😆 | 18:12:32 |
|  nullbite joined the room. | 19:00:30 |
|  @_oftc_myme:matrix.org joined the room. | 19:17:59 |
|  myme1 left the room. | 19:20:40 |
|  rosariopulella changed their display name from Rosario Pulella to Rosuavio. | 20:08:04 |
| @_oftc___monty__:matrix.org left the room. | 21:18:55 |
 522 | does https://www.freedesktop.org/software/systemd/man/latest/loginctl.html#enable-linger%20USER%E2%80%A6 help?
Enable/disable user lingering for one or more users. If enabled for a specific user, a user manager is spawned for the user at boot and kept around after logouts. This allows users who are not logged in to run long-running services.
seems like what you want?
| 21:34:02 |
| 522 | (though note: haven't tried it myself) | 21:34:16 |
| 2 May 2025 |
| musicmatze | In reply to @r522:matrix.org
does https://www.freedesktop.org/software/systemd/man/latest/loginctl.html#enable-linger%20USER%E2%80%A6 help?
Enable/disable user lingering for one or more users. If enabled for a specific user, a user manager is spawned for the user at boot and kept around after logouts. This allows users who are not logged in to run long-running services.
seems like what you want?
Cool that sounds exactly like what I need, thanks | 05:17:34 |
|  @_oftc_al3xtjames:matrix.org left the room. | 08:56:59 |
|  al3xtjames2 joined the room. | 08:57:13 |
|  @_oftc_bigrick:matrix.org left the room. | 15:01:07 |
| @_oftc_bigrick:matrix.org joined the room. | 16:21:53 |
