Lines Matching full:uuid
2242 this UUID may be used to distinguish one server address from another. A
2243 server should use a different UUID for each address it listens on. For
2251 The intent of the address UUID feature is to allow a client to avoid
2262 rest of the API and documentation says "UUID," for historical reasons.
2328 First, each server address has a UUID identifying the address,
2330 system kernel instance running a D-Bus client or server has a UUID
2336 The term "UUID" in this document is intended literally, i.e. an
2338 RFC4122, and in fact the D-Bus UUID is not compatible with that RFC.
2341 The UUID must contain 128 bits of data and be hex-encoded. The
2344 UUID, the current reference implementation concatenates 96 bits of random
2357 of the UUID.
2389 UUID representing the identity of the machine the process is running on.
2390 This UUID must be the same for all processes on a single system at least
2398 The UUID is intended to be per-instance-of-the-operating-system, so may represent
2400 Basically if two processes see the same UUID, they should also see the same
2405 The UUID is often used where other programs might use a hostname. Hostnames
2406 can change without rebooting, however, or just be "localhost" - so the UUID
2410 <xref linkend="uuids"/> explains the format of the UUID.
