SD_BUS_MESSAGE_SEAL(3)

💖 SD_BUS_MESSAGE_SEAL(3) — the sd_bus_message_seal(3) manual page, but make it cute 💖

okay bestie, welcome to the sd_bus_message_seal(3) manual page. This is your D-Bus message seal glow-up moment, and yes, it’s gonna be useful. 💅✨

🌸 NAME 🌸

• sd_bus_message_seal — prepares a D-Bus message for transmission. It’s giving “last little seal before send-off” energy. 🎀

✨ SYNOPSIS ✨

#include <systemd/sd-bus.h>

int sd_bus_message_seal(sd_bus_message *m, uint64_t cookie,
                        uint64_t timeout_usec);

🦋 DESCRIPTION 🦋

sd_bus_message_seal() finishes the message m and prepares it for transmission using sd_bus_send(3). 🫶

cookie is the identifier used to match the message reply to its corresponding request. timeout_usec is the maximum time, in microseconds, to wait for a reply to arrive. ⏳

💀 real talk: in most scenarios, you do not need to call this function directly. sd_bus_call(3), sd_bus_call_async(3), and sd_bus_send(3) will seal any given messages if they have not been sealed yet. so like, they got you. no cap. 🫶

⭐ RETURN VALUE ⭐

On success, this function returns a non-negative integer. 😌 On failure, it returns a negative errno-style error code. 😭

💀 Errors 💀

Returned errors may indicate the following problems:

• -EINVAL — the m parameter is NULL. Added in version 246.
• -EBADMSG — the D-Bus message m has open containers. Added in version 246.
• -ENOMSG — the D-Bus message m is a reply but its type signature does not match the return type signature of its corresponding member in the object vtable. Added in version 246.

📝 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. ⚠️

🕰️ HISTORY 🕰️

sd_bus_message_seal() was added in version 246. 👑

👀 SEE ALSO 👀

systemd(1), sd-bus(3), sd_bus_call(3), sd_bus_call_async(3), sd_bus_send(3)

---

okay that’s the whole page, mwah 💋 this cutie is from systemd 261.3, the SD_BUS_MESSAGE_SEAL(3) page, and the footer didn’t give me a date so I’m not inventing one, bestie 🎀🌈