succeeded attributes
| status |
attribute |
duration |
| succeeded |
checks.aarch64-linux.systemd-journal
- system.stateVersion is not set, defaulting to 26.11. Read why this matters on https://nixos.org/manual/nixos/stable/options.html#opt-system.stateVersion.
|
3m 52s |
| succeeded |
checks.aarch64-linux.systemd-oomd
- The option `systemd.oomd.extraConfig' defined in `/nix/store/mfaj27iam74lx445ppslfjnb0nsz7ww8-source/nixos/tests/systemd-oomd.nix' has been renamed to `systemd.oomd.settings.OOM'.
|
1m 36s |
| succeeded |
checks.aarch64-linux.systemd-shutdown
- Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes.
|
2m 9s |
| succeeded |
checks.aarch64-linux.systemd-sysusers-password-option-override-ordering
- The user 'alice' has multiple of the options
`initialHashedPassword`, `hashedPassword`, `initialPassword`, `password`
& `hashedPasswordFile` set to a non-null value.
If multiple of these password options are set at the same time then a
specific order of precedence is followed, which can lead to surprising
results. The order of precedence differs depending on whether the
{option}`users.mutableUsers` option is set.
If the option {option}`users.mutableUsers` is
`true`, then the order of precedence is as shown
below, where values on the left are overridden by values on the right:
{option}`initialHashedPassword` -> {option}`initialPassword` -> {option}`hashedPassword` -> {option}`password` -> {option}`hashedPasswordFile`
The values of these options are:
* users.users."alice".hashedPassword: null
* users.users."alice".hashedPasswordFile: null
* users.users."alice".password: null
* users.users."alice".initialHashedPassword: "$y$j9T$wLgKY231.8j.ciV2MfEXe1$P0k5j3bCwHgnwW0Ive3w4knrgpiA4TzhCYLAnHvDZ51"
* users.users."alice".initialPassword: "test"
- The user 'bob' has multiple of the options
`initialHashedPassword`, `hashedPassword`, `initialPassword`, `password`
& `hashedPasswordFile` set to a non-null value.
If multiple of these password options are set at the same time then a
specific order of precedence is followed, which can lead to surprising
results. The order of precedence differs depending on whether the
{option}`users.mutableUsers` option is set.
If the option {option}`users.mutableUsers` is
`true`, then the order of precedence is as shown
below, where values on the left are overridden by values on the right:
{option}`initialHashedPassword` -> {option}`initialPassword` -> {option}`hashedPassword` -> {option}`password` -> {option}`hashedPasswordFile`
The values of these options are:
* users.users."bob".hashedPassword: null
* users.users."bob".hashedPasswordFile: "/nix/store/j5issrx4q7zkwrp2g11w6ymcajqsfhmz-hashed-password"
* users.users."bob".password: null
* users.users."bob".initialHashedPassword: "$y$j9T$wLgKY231.8j.ciV2MfEXe1$P0k5j3bCwHgnwW0Ive3w4knrgpiA4TzhCYLAnHvDZ51"
* users.users."bob".initialPassword: "test"
|
2m 1s |
| succeeded |
checks.aarch64-linux.systemd-userdbd
- The following system users have UIDs higher than 1000:
nixbld1
nixbld10
nixbld11
nixbld12
nixbld13
nixbld14
nixbld15
nixbld16
nixbld17
nixbld18
nixbld19
nixbld2
nixbld20
nixbld21
nixbld22
nixbld23
nixbld24
nixbld25
nixbld26
nixbld27
nixbld28
nixbld29
nixbld3
nixbld30
nixbld31
nixbld32
nixbld4
nixbld5
nixbld6
nixbld7
nixbld8
nixbld9
These users will be recognized by systemd-userdb as "regular" users, not
"system" users. This will affect programs that query regular users, such
as systemd-homed, which will not run the first boot user creation flow,
as regular users already exist.
To fix this issue, please remove or redefine these system users to have
UIDs below 1000. For Nix build users, it's possible to adjust the base
build user ID using the `ids.uids.nixbld` option, however care must be
taken to avoid collisions with UIDs of other services. Alternatively, you
may enable the `auto-allocate-uids` experimental feature and option in
the Nix configuration to avoid creating these users, however please note
that this option is experimental and subject to change.
Alternatively, to acknowledge and silence this warning, set
`services.userdbd.silenceHighSystemUsers` to true.
|
1m 47s |
| succeeded |
checks.aarch64-linux.fsck-systemd-stage-1
|
4m 53s |
| succeeded |
checks.aarch64-linux.simple-vm
|
4m 44s |
| succeeded |
checks.aarch64-linux.systemd
|
6m 33s |
| succeeded |
checks.aarch64-linux.systemd-analyze
|
4m 53s |
| succeeded |
checks.aarch64-linux.systemd-bpf
|
3m 31s |
| succeeded |
checks.aarch64-linux.systemd-coredump
|
3m 26s |
| succeeded |
checks.aarch64-linux.systemd-credentials-tpm2
|
3m 24s |
| succeeded |
checks.aarch64-linux.systemd-cryptenroll
|
3m 52s |
| succeeded |
checks.aarch64-linux.systemd-escaping
|
3m 18s |
| succeeded |
checks.aarch64-linux.systemd-initrd-modprobe
|
2m 53s |
| succeeded |
checks.aarch64-linux.systemd-initrd-networkd-basic
|
3m 8s |
| succeeded |
checks.aarch64-linux.systemd-initrd-networkd-doFlush
|
2m 48s |
| succeeded |
checks.aarch64-linux.systemd-initrd-networkd-dontFlush
|
2m 47s |
| succeeded |
checks.aarch64-linux.systemd-initrd-networkd-ssh
|
2m 57s |
| succeeded |
checks.aarch64-linux.systemd-initrd-shutdown
|
2m 25s |
| succeeded |
checks.aarch64-linux.systemd-initrd-simple
|
2m 56s |
| succeeded |
checks.aarch64-linux.systemd-initrd-vlan
|
2m 30s |
| succeeded |
checks.aarch64-linux.systemd-journal-gateway
|
2m 33s |
| succeeded |
checks.aarch64-linux.systemd-journal-upload
|
2m 42s |
| succeeded |
checks.aarch64-linux.systemd-misc
|
2m 24s |
| succeeded |
checks.aarch64-linux.systemd-networkd
|
2m 24s |
| succeeded |
checks.aarch64-linux.systemd-networkd-bridge
|
2m 57s |
| succeeded |
checks.aarch64-linux.systemd-networkd-dhcpserver
|
1m 58s |
| succeeded |
checks.aarch64-linux.systemd-networkd-dhcpserver-static-leases
|
1m 55s |
| succeeded |
checks.aarch64-linux.systemd-networkd-vrf
|
2m 30s |
| succeeded |
checks.aarch64-linux.systemd-no-tainted
|
1m 40s |
| succeeded |
checks.aarch64-linux.systemd-nspawn
|
2m 10s |
| succeeded |
checks.aarch64-linux.systemd-nspawn-configfile
|
1m 25s |
| succeeded |
checks.aarch64-linux.systemd-portabled
|
1m 20s |
| succeeded |
checks.aarch64-linux.systemd-pstore
|
2m 49s |
| succeeded |
checks.aarch64-linux.systemd-resolved
|
2m 6s |
| succeeded |
checks.aarch64-linux.systemd-sysupdate
|
2m 10s |
| succeeded |
checks.aarch64-linux.systemd-sysusers-immutable
|
2m 6s |
| succeeded |
checks.aarch64-linux.systemd-sysusers-mutable
|
2m 20s |
| succeeded |
checks.aarch64-linux.systemd-timesyncd
|
1m 47s |
| succeeded |
checks.aarch64-linux.systemd-user-linger
|
1m 55s |
| succeeded |
checks.aarch64-linux.systemd-user-tmpfiles-rules
|
2m 49s |