UDEV_MON...M_NETLINK(3)

okay bestie, you're looking at the UDEV_MON...M_NETLINK(3) manual page, and it's giving “three libudev functions with one little create/acquire/release situation.” no cap 💅

🦋 NAME 🦋

udev_monitor_new_from_netlink, udev_monitor_ref, udev_monitor_unref — create, acquire and release a udev monitor object. that's the whole assignment, bestie 🫶

---

✨ SYNOPSIS ✨

#include <libudev.h>

struct udev_monitor *udev_monitor_new_from_netlink(struct udev *udev,
                                                   const char *name);

struct udev_monitor *udev_monitor_ref(struct udev_monitor *udev_monitor);

struct udev_monitor *udev_monitor_unref(struct udev_monitor *udev_monitor);

---

🎀 RETURN VALUE 🎀

• On success, udev_monitor_new_from_netlink() returns a pointer to the allocated udev monitor. On failure, NULL is returned. slay when it works, sad little NULL when it doesn't 😭
• udev_monitor_ref() returns the argument that it was passed, unmodified. it literally hands you back the same thing, no edits, no glow-up, periodt.
• udev_monitor_unref() always returns NULL. every single time, bestie. that's its whole thing 💀

---

🌈 HISTORY 🌈

• udev_monitor_new_from_netlink(), udev_monitor_ref(), and udev_monitor_unref() were added in version 221. iconic behavior from way back, fr fr ✨

---

💜 SEE ALSO 💜

• udev_new(3)
• udev_device_new_from_syspath(3)
• udev_enumerate_new(3)
• udev_monitor_filter_update(3)
• udev_monitor_receive_device(3)
• udev_list_entry(3)
• systemd(1)

---

that's the whole page, no cap 🫶 the footer has systemd 261.3 and the label UDEV_MON...M_NETLINK(3) — no date in sight, just vibes and version info, bestie 💖