S6-FDHOLDER-SETDUMP(8)

📦 version 2.15.1.0, in nixpkgs unstable

💅 s6-fdholder-setdump(8) — the fd-dumping bestie manual 💅

okay so bestie, this is the section 8, System Manager's Manual page for s6-fdholder-setdump, and it is literally about connecting to an s6-fdholderd(8) daemon listening on a Unix domain socket and dumping a set of file descriptors into that daemon. ✨

🌸 NAME 🌸

s6-fdholder-setdump — connect to an s6-fdholderd(8) daemon listening on a Unix domain socket, and dump a set of file descriptors into that daemon. 🫶

⭐ SYNOPSIS ⭐

s6-fdholder-setdump [-t timeout] path

🦋 DESCRIPTION 🦋

s6-fdholder-setdump connects to an s6-fdholderd(8) server process listening on path. 💖

It attempts to pass a complete state — i.e. a set of file descriptors with identifiers and expiration dates — to the server. no cap, that is the whole vibe.

The file descriptors to transmit to the server should of course already be open in the s6-fdholder-setdump program; also, s6-fdholder-setdump should have certain environment variables that describe that set of file descriptors. The format of the environment is the same as the one set by s6-fdholder-getdump(8). 👑

Setting the whole state of an s6-fdholderd(8) daemon requires specific privileges. Make sure you properly configure s6-fdholderd(8) access rights so your client can perform that operation. 🔐

Previously held fds will still be kept by the server (so, “setting” the state is more like “adding to” the state), unless there is an identifier collision, in which case the fd in the transmitted set takes precedence and the previously held fd is overwritten. that is the tea. ☕

🎀 OPTIONS 🎀

  • -t timeout — if the operation cannot be processed in timeout milliseconds, then fail with an error message. Communications with the server should be near-instant, so this option is only here to protect users against programming errors (connecting to the wrong socket, for instance). 💀

🔥 EXIT STATUS 🔥

  • 0 — Success. 🎉
  • 1 — The server denied the operation. The meanings of the error messages are explained in s6-fdholder-error-codes(7).
  • 100 — Wrong usage. 🚫
  • 111 — System call failed — this includes attempting to connect to a nonexistent socket, or one where no s6-fdholderd(8) daemon is listening. 😭

🌈 SEE ALSO 🌈

This man page is ported from the authoritative documentation at: https://skarnet.org/software/s6/s6-fdholder-setdump.html

👑 AUTHORS 👑

Laurent Bercot Alexis <flexibeast@gmail.com> (man page port)

and that is the cute sign-off, bestie: this whole page is coming at you from the Debian man page source, dated September 29, 2021. mwah 💋🎀

📦 where this page comes from