Lines Matching refs:top

101 1. Various fields are placed at the top-level of user record (the `regular`
121    accepted in the `perMachine` section can also be set at the top level (the
210 As mentioned, the `regular` section's fields are placed at the top level
420 the top-level directory of the CIFS share is used.
468 the loopback block devices, LUKS and the file system on top shall be used in
616 record top-level object, in the `privileged` field. Any data included in this
698 The `perMachine` field in the top-level object is an array of objects. When
699 processing the user record first the various fields on the top-level object
704 set in the top-level object as in a per-machine object the latter wins and
705 entirely undoes the setting in the top-level object (i.e. no merging of
725 `regular` section (i.e. at the top-level object). Specifically, these are:
761 The `binding` sub-object on the top-level user record object is keyed by the
791 sub-object of the top-level user record object is keyed by the machine ID,
809 different things (see above). In contrast to the top-level field of the same
833 top-level object (i.e. in the `regular` section), which it overrides. The
897 The `signature` field in the top-level user record object is an array of
950 The `secret` field of the top-level user record contains the following fields: