Lines Matching refs:when
110 password hashes and more. Algorithmically, when a user record is passed to
135 calculated on. In `systemd-homed` this section is also removed when the
158 covered by the signature. This section is optional, and is only used when
163 PIN information. This data is never persisted, and never returned when user
165 be included in a user record very briefly, for example when certain very
167 `systemd-homed` this section may be included in user records, when creating
193 the fields included therein are only useful when executing authentication
229 optional, when unset the user should not be considered part of any realm. A
237 vice versa when converting back. That said, unlike GECOS this field is supposed
273 since the epoch 1970, indicating when the user record (specifically, any of the
275 used when comparing two records of the same user to identify the newer one, and
347 `struct spwd`, when it is set to a value larger than one, but provides finer
360 `systemd-homed` when managing home directories, but may be used if other
375 directory to populate a new home directory from. This is only used when a home
379 access mask for the home directory when it is first created.
409 use. This is generally useful, but particularly when `cifs` is used as storage
414 useful when `cifs` is used as storage mechanism for the user's home directory,
423 `mount.cifs` when mounting the home directory CIFS share.
452 when the storage mechanism used is `luks` as a file system to use inside the
457 relevant when the storage mechanism used is `luks`.
461 relevant when the storage mechanism used is `luks`.
465 primarily relevant when the storage mechanism used is `luks`.
475 to trim/allocate the file system/backing file when deactivating the home
494 time cost for the PBKDF operation, when the LUKS storage mechanism is used, in
498 memory cost for the PBKDF operation, when LUKS storage is used, in bytes.
501 required parallel threads for the PBKDF operation, when LUKS storage is used.
531 password policy when creating the home directory for the user or changing the
543 set to zero the per-user service manager is immediately terminated when the
549 automatically killed when the user logs out. This is enforced by
551 false any processes left around when the user logs out are left running.
618 be suppressed implicitly when other users get access to a user record. It thus
687 automatically into normalized form, i.e. the dashes inserted when missing, and
720 within the same array entry, the object is honored when either match succeeds,
755 suppressed when the user record is ported between systems. The `binding` section
788 only acquired "on-the-fly" when requested.
811 allotted to the user, not the intended one. The values may differ when user
815 bounds when changing the `diskSize` value, in bytes. These values are typically
891 is optional, and only used when cryptographic validation of user records shall
947 for example when a user record is first created or registered, as the secret