SD_BUS_GET_NAME_MACHINE_ID(3)

💖 sd_bus_get_name_machine_id(3) 💖

okay bestie, you’re looking at the systemd manual page named SD_BUS_GET...MACHINE_ID(3) — yes, the truncated header is right there, and the main character is sd_bus_get_name_machine_id, section 3. 🦋

✨ NAME ✨

sd_bus_get_name_machine_id — retrieve a bus client's machine identity. periodt.

---

🌸 SYNOPSIS 🌸

       #include <systemd/sd-bus.h>

       int sd_bus_get_name_machine_id(sd_bus *bus, const char *name,
                                      sd_id128_t *machine);

🎀 DESCRIPTION 🎀

So like, sd_bus_get_name_machine_id() retrieves the D-Bus machine identity of the machine that the bus client identified by name is running on. 💅 Internally, it calls the GetMachineId method of the org.freedesktop.DBus.Peer interface. The D-Bus machine identity is a 128-bit UUID. On Linux systems running systemd, this corresponds to the contents of /etc/machine-id. On success, the machine identity is stored in machine. slay.

🔥 RETURN VALUE 🔥

On success, this function returns a non-negative integer. On failure, it returns a negative errno-style error code. that’s the whole deal.

😭 Errors 😭

Returned errors may indicate the following problems, bestie:

• -EINVAL — an argument is invalid. rude.
• -ENOPKG — the bus cannot be resolved. it’s giving unresolved-bus energy.
• -ECHILD — the bus was created in a different process, library or module instance. awkward.
• -ENOMEM — memory allocation failed. 💀

🧚 NOTES 🧚

Functions described here are available as a shared library, which can be compiled against and linked to with the libsystemd pkg-config(1) file. 🫶

All functions listed here are thread-agnostic and only a single thread may operate on a given object at any given time. Different threads may access the same object at different times. Multiple independent objects may be used from different threads in parallel.

The code described here uses getenv(3), which is declared to be not multi-thread-safe. This means that the code calling the functions described here must not call setenv(3) from a parallel thread. It is recommended to only do calls to setenv() from an early phase of the program when no other threads have been started. fr fr.

⚠️ caveat: that setenv(3) rule is not a suggestion, bestie — don’t be calling it from a parallel thread while this code is doing its thing.

👑 HISTORY 👑

sd_bus_get_name_machine_id() was added in version 221. iconic behavior.

🌈 SEE ALSO 🌈

• systemd(1)
• sd-bus(3)

---

cute sign-off: this page comes from systemd 261.3, and the footer label is SD_BUS_GET...MACHINE_ID(3). the original footer didn’t print a date, so no fake date from me, bestie 💅✨