Home
last modified time | relevance | path

Searched refs:fields (Results 1 – 25 of 35) sorted by relevance

12

/systemd-251/src/sysupdate/
Dsysupdate-pattern.c450 const InstanceMetadata *fields, in pattern_format() argument
458 assert(fields); in pattern_format()
476 if (!fields->version) in pattern_format()
479 if (!strextend(&j, fields->version)) in pattern_format()
486 if (!fields->partition_uuid_set) in pattern_format()
489 if (!strextend(&j, sd_id128_to_string(fields->partition_uuid, formatted))) in pattern_format()
496 if (!fields->partition_flags_set) in pattern_format()
499 r = strextendf(&j, "%" PRIx64, fields->partition_flags); in pattern_format()
506 if (fields->mtime == USEC_INFINITY) in pattern_format()
509 r = strextendf(&j, "%" PRIu64, fields->mtime); in pattern_format()
[all …]
Dsysupdate-pattern.h12 int pattern_format(const char *pattern, const InstanceMetadata *fields, char **ret);
/systemd-251/test/units/
Dtestsuite-04.sh72 journalctl -b -o export --output-fields=MESSAGE,FOO --output-fields=PRIORITY,MESSAGE -t "$ID" >/out…
100 journalctl -b -o export -t "$ID" --output-fields=_PID | grep '^_PID=' >/output
112 [[ $(journalctl -b -o cat -t "$ID" --output-fields=_TRANSPORT | grep -Pc "^stdout$") -eq 3 ]]
113 [[ $(journalctl -b -o cat -t "$ID" --output-fields=_LINE_BREAK | grep -Pc "^pid-change$") -eq 3 ]]
114 [[ $(journalctl -b -o cat -t "$ID" --output-fields=_PID | sort -u | grep -c "^.*$") -eq 3 ]]
115 [[ $(journalctl -b -o cat -t "$ID" --output-fields=MESSAGE | grep -Pc "^(This will|usually fail|and…
/systemd-251/docs/
DGROUP_RECORD.md15 they carry some identical (or at least very similar) fields.
63 The following fields are defined:
75 The following fields are defined for the `perMachine` section and are defined
76 equivalent to the fields of the same name in the `regular` section, and
83 The following fields are defined for the `binding` section, and are equivalent
84 to the fields of the same name in the `regular` and `perMachine` sections:
90 The following fields are defined in the `status` section, and are mostly
91 equivalent to the fields of the same name in the `regular` section, though with
92 slightly different conceptual semantics, see the same fields in the user record
99 The fields in this section are defined identically to those in the matching
[all …]
DJOURNAL_EXPORT_FORMATS.md16 …ntries](https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html), in particul…
21 …fields consisting only of valid non-control UTF-8 codepoints are serialized as they are (i.e. the …
22 * Other journal fields are serialized in a special binary safe way: field name, followed by newline…
23 …fields are only generated when actual journal files are serialized. They are omitted for entries t…
24 * The order in which fields appear in an entry is undefined and might be different for each entry t…
129 …ntries](https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html), in particul…
134 * The JSON serializer can optionally skip huge (as in larger than a specific threshold) data fields…
135 * Within the same entry, Journal fields may have multiple values assigned. This is not allowed in J…
136 * If the JSON data originates from a journal file it may include the special addressing fields `__C…
DUSER_RECORD.md45 JSON user records may contain various fields that are not available in `struct
101 1. Various fields are placed at the top-level of user record (the `regular`
102 section). These are generally fields that shall apply unconditionally to the
105 2. A number of fields are located in the `privileged` section (a sub-object of
114 3. A number of fields are located in objects inside the `perMachine` section
116 management-related fields, as those tend to make sense on a specific system
120 which systems to apply the listed settings to. Note that many fields
125 4. Various fields are located in the `binding` section (a sub-sub-object of the
138 `binding` fields individually. Typically, the binding section is persisted
141 5. Various fields are located in the `status` section (a sub-sub-object of the
[all …]
DJOURNAL_NATIVE_PROTOCOL.md97 recommended to generate these fields implicitly on the client side. For further
99 fields](https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html).
101 The order in which the fields are serialized within one datagram is undefined
113 just fine, and it's generally preferred to have a single set of metadata fields
120 used for specific Journal fields however, where this is expected. Do not use
121 this for Journal fields where this is not expected and where code reasonably
123 displays log entries is likely to ignore such non-unique fields or only
125 contains multiple `MESSAGE=` fields, likely only the first one is
133 Here's an encoded message, with various common fields, all encoded according to
170 the STDERR file descriptor. If the `.st_dev` and `.st_ino` fields of the
DGVARIANT-SERIALIZATION.md15 2. Additional header fields of "a(yv)"
34 This header is then followed by the fields array, whose first value is
50 This is then followed by the GVariant fields array ("a{tv}"), and
87 consider that on dbus1 the beginning of the fields array contains the
103 fixed header and additional header fields in a single non-memfd
DJOURNAL_FILE_FORMAT.md16 * Fully indexed by all fields
57 entries](https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html),
102 All fields marked as "reserved" must be initialized with 0 when writing and be
242 **incompatible_flags** field. Readers should check these two bit fields, if
246 there's an unknown bit flag in either of these fields.
249 header is stored in the header. All header fields up to **n_data** are known to
250 unconditionally exist in all revisions of the file format, all fields starting
254 Currently only five extensions flagged in the flags fields are known:
528 **field_hash_table_offset**, **field_hash_table_size** fields. These offsets do
540 number of fields should be pretty static as it depends only on developers'
[all …]
DUSERDB_AND_DESKTOPS.md75 fields of relevance to UIs that manage the local user database or parts
95 exposed in a user management UI. Various metadata fields are supplied allowing
155 fields desktop environments require. For example pattern-based authentication
DBUILDING_IMAGES.md253 identify them and their version. For this the two fields `IMAGE_ID=` and
256 fields may be accessed from unit files and similar via the `%M` and `%A`
263 fields.
DHOME_DIRECTORY.md23 record into 'normalized' form (i.e. all objects should contain their fields
58 pair of Base64 encoded data fields. The first field contains a salt value, the
DBOOT_LOADER_SPECIFICATION.md242 decreasing, i.e. newest version first) fields described above are used as
350 The `PRETTY_NAME=` and `VERSION_ID=` fields in the embedded os-release file are
353 and `initrd` fields are not necessary, and there is no counterpart for the
384 on the `sort-key`, `machine-id` and `version` fields, and possibly others. It
DCONVERTING_TO_HOMED.md58 user. For details about the fields, see the respective man pages
DCOREDUMP_PACKAGE_METADATA.md59 "type":"rpm", # this provides a namespace for the package+package-version fields
/systemd-251/shell-completion/zsh/
D_journalctl19 yes) _values -s '=' 'possible fields' \
21 *) _describe 'possible fields' journal_fields ;;
34 'fields:fields:_journalctl_fields'
41 _fields=$(_call_program fields $cmd[@])
96 {-l,--full}'[Show long fields in full]' \
97 {-a,--all}'[Show all fields, including long and unprintable]' \
/systemd-251/tools/
Dcatalog-report.py77 fields = [field[1:-1] for field in pattern.findall(desc)] variable
78 for field in fields:
/systemd-251/shell-completion/bash/
Djournalctl47 --flush --rotate --sync --no-hostname -N --fields'
53 --vacuum-size --vacuum-time --vacuum-files --output-fields'
80 comps=$(journalctl --fields | sort 2>/dev/null)
147 mapfile -t field_vals < <(journalctl --fields 2>/dev/null)
/systemd-251/src/shared/
Dlogs-show.c170 static int parse_fieldv(const void *data, size_t length, const ParseFieldVec *fields, unsigned n_fi… in parse_fieldv() argument
174 const ParseFieldVec *f = &fields[i]; in parse_fieldv()
187 static int field_set_test(const Set *fields, const char *name, size_t n) { in field_set_test() argument
190 if (!fields) in field_set_test()
194 return set_contains(fields, s); in field_set_test()
448 const ParseFieldVec fields[] = { in output_short() local
478 r = parse_fieldv(data, length, fields, ELEMENTSOF(fields)); in output_short()
1267 _cleanup_set_free_ Set *fields = NULL; in show_journal_entry() local
1276 r = set_put_strdupv(&fields, output_fields); in show_journal_entry()
1280 r = output_funcs[mode](f, j, mode, n_columns, flags, fields, highlight); in show_journal_entry()
/systemd-251/test/
Dnetworkd-test.py172 fields = line.split()
173 if len(fields) >= 5 and fields[1] in kwargs:
174 iface = fields[1]
176 actual = fields[-1]
/systemd-251/test/test-sysusers/
Dtest-2.input3 # replacement of all fields up to the login shell.
/systemd-251/LICENSES/
DOFL-1.1.txt64 in the appropriate machine-readable metadata fields within text or
65 binary files as long as those fields can be easily viewed by the user.
/systemd-251/units/
Dsystemd-firstboot.service29 # Optionally, pick up basic fields from credentials passed to the service
Dsystemd-journald.service.in46 # the _EXE=/OBJECT_EXE= fields will be missing from the journal entries.
/systemd-251/hwdb.d/
D60-evdev.hwdb29 # min, max, res, fuzz, flat are the decimal values to the respective fields of
31 # the field will be left as-is. Not all fields need to be present. e.g. ::45

12