home-manager/tests/modules/systemd/default.nix

{
  systemd-services = ./services.nix;
  systemd-services-disabled-for-root = ./services-disabled-for-root.nix;
  systemd-session-variables = ./session-variables.nix;
  systemd-user-config = ./user-config.nix;
  systemd-empty-user-config = ./empty-user-config.nix;
  systemd-slices = ./slices.nix;
  systemd-timers = ./timers.nix;
}
systemd: add some basic tests 2019-03-24 15:52:30 +01:00			`{`
			`systemd-services = ./services.nix;`
systemd: do not install systemd files when user is root (#2454) For the user root, there are no user services provided by systemd. Therefore, these files will never be used. 2021-11-23 07:06:43 +01:00			`systemd-services-disabled-for-root = ./services-disabled-for-root.nix;`
systemd: add support for session variables Via environment.d(5). 2019-03-22 12:47:49 +01:00			`systemd-session-variables = ./session-variables.nix;`
systemd: add settings option (#4276) The `systemd.user.extraConfig` provides a way to generate a `systemd-user.conf(5)` file for the user. This is the home-manager equivalent of NixOS’s option of the same name, with the difference that NixOS’s option generates a `user.conf` file that is shared between all users. 2023-11-07 15:55:17 +01:00			`systemd-user-config = ./user-config.nix;`
systemd: avoid creating an empty user.conf Due to the defaults in `systemd.user.settings`, the default value when there are no settings explicitly set is `{ Manager = { }; }`. This means an empty file is created even when `systemd.user.settings` is never used in home-manager configuration. Since user’s `user.conf` is preferred to the global `/etc/systemd/user.conf`, this can cause any values set in the latter to be discarded. 2023-11-11 00:51:53 +01:00			`systemd-empty-user-config = ./empty-user-config.nix;`
systemd: name slice unit correctly 2022-10-07 06:49:39 +02:00			`systemd-slices = ./slices.nix;`
systemd: add some basic tests 2019-03-24 15:52:30 +01:00			`systemd-timers = ./timers.nix;`
			`}`