Lines Matching refs:field

59 usually don't), and the same field might have multiple values assigned within
133 …field of an entry, i.e. a string such as `_SYSTEMD_UNIT=avahi-daemon.service`, or `MESSAGE=Foobar …
134 * A **FIELD** object, which encapsulates a field name, i.e. a string such as `_SYSTEMD_UNIT` or `ME…
196 **arena_size** field of the header. If a writer needs to write to a file where
202 The **n_objects** field contains a counter for objects currently available in
232 field hash table, minus one.
240 header's **compatible_flags** field. If a feature extension is used that makes
242 **incompatible_flags** field. Readers should check these two bit fields, if
294 If a file is opened for writing the **state** field should be set to
295 STATE_ONLINE. If a file is closed after writing the **state** field should be
301 After and before the state field is changed, `fdatasync()` should be executed on
309 **seqnum_id** field. This field is randomly generated when the journal daemon
324 field in the file header (see below). It is recommended to execute a memory
374 The **type** field is one of the object types listed above. The **flags** field
381 set. The **size** field encodes the size of the object including all its
400 Data objects carry actual field data in the **payload[]** array, including a
401 field name, a `=` and the field data. Example:
402 `_SYSTEMD_UNIT=foobar.service`. The **hash** field is a hash value of the
405 in the **file_id** field of the file header. If the flag is not set it is the
413 the same field name from the FIELD object of the field used.
424 The **payload[]** field contains the field name and date unencoded, unless
442 Field objects are used to enumerate all possible values a certain field name
445 The **payload[]** array contains the actual field name, without '=' or any
446 field value. Example: `_SYSTEMD_UNIT`. The **hash** field is a hash value of
453 field name. It is the head of a singly linked list using DATA's
479 The **seqnum** field contains the sequence number of the entry, **realtime**
483 The **xor_hash** field contains a binary XOR of the hashes of the payload of
488 used hash function) the hash function used for this field, as singular
522 objects, respectively. DATA's and FIELD's next_hash_offset field are used to
560 allocated and the **next_entry_array_offset** field of the old one pointed to
569 first entry array is referenced in the **entry_array_offset** field of the
621 starting with the headers' **entry_array_offset** field.
625 **entry_array_offset** field. Since these arrays double in size as more are
629 When seeking or listing with one field match applied the DATA object of the
639 well-known fields, where the set of possible field values tend to be closely
649 When listing all possible values a certain field can take it is sufficient to
655 hash table should be checked. If the data field does not yet exist in the file,
656 it should be appended and added to the data hash table. When a data field's data
657 object is added, the field hash table should be checked for the field name of
658 the data field, and a field object be added if necessary. After all data fields
659 (and recursively all field names) of the new entry are appended and linked up