systemd-id128 — Generate and print sd-128 identifiers
systemd-id128
[OPTIONS...] new
systemd-id128
[OPTIONS...] machine-id
systemd-id128
[OPTIONS...] boot-id
systemd-id128
[OPTIONS...] invocation-id
id128 may be used to conveniently print sd-id128(3) UUIDs. What identifier is printed depends on the specific verb.
With new, a new random identifier will be generated.
With machine-id, the identifier of the current machine will be printed. See machine-id(5).
With boot-id, the identifier of the current boot will be printed.
Both machine-id and boot-id may be combined
with the --app-specific=
switch to
generate application-specific IDs. See
sd_id128_get_machine(3)
for the discussion when this is useful.app-id
With invocation-id, the identifier of the current service invocation will be printed. This is available in systemd services. See systemd.exec(5).
The following options are understood:
-p
, --pretty
¶Generate output as programming language snippets.
-a app-id
, --app-specific=app-id
¶With this option, an identifier that is the result of hashing the
application identifier app-id
and the machine identifier will be
printed. The app-id
argument must be a valid sd-id128 string
identifying the application.
-u
, --uuid
¶Generate output as an UUID formatted in the "canonical representation", with five groups of digits seperated by hyphens. See the wikipedia for more discussion.
-h
, --help
¶--version
¶