seatd-launch(1)

✨ seatd-launch(1) ✨

okay bestie, this is the seatd-launch page from the General Commands Manual, and it is literally the little helper that gets you your own private seatd. buckle up πŸŽ€


🌸 NAME 🌸

seatd-launch β€” start a process with its own seatd instance πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

seatd-launch [options] [--] command

πŸ’– OPTIONS πŸ’–

  • -l <loglevel> β€” the log-level you wanna hand off to seatd. want the deets on which log-levels exist? go peek at seatd(1), it's all there, no cap.
  • -h β€” show the help message and dip. that's it, that's the whole job πŸ™ˆ
  • -v β€” show the version number and dip. iconic behaviour honestly πŸ‘‘

✨ DESCRIPTION ✨

so here's the vibe: seatd-launch spins up a seatd instance with its very own dedicated socket path, waits for it to be ready ready, and then starts the command you asked for with SEATD_SOCK set appropriately. and the way that it's obsessed with cleanup?? the moment your command terminates, the seatd instance gets terminated too. periodt. 🫢

now, seatd needs root privileges to do its whole thing. you can get there two ways: SUID on seatd-launch, or just running seatd-launch as root. seatd-launch will drop privileges from the effective user down to the real user before running your command β€” and if the real user is root, that's simply a noop, so nothing happens there. ⚠️ but listen: you should only run seatd-launch as root if you intend for the specified command to run as root as well. like, actually intend it. fr fr.

seatd-launch serves a similar purpose to the libseat "builtin" backend, but bestie it is superior to it for two reasons:

  1. The specified command never runs as root 🌈
  2. The standard seatd executable and libseat backend is used πŸ‘‘

πŸ”₯ EXIT STATUS πŸ”₯

seatd-launch exits with the status of its child. and if the child terminates on a signal N, then seatd-launch exits with the status 128 + N. math is math πŸ’€

if seatd-launch fails because of another error, it exits with a non-zero status. that's your red flag, bestie.


🌈 SEE ALSO 🌈

The libseat library, <libseat.h>, seatd(1)


πŸ’œ AUTHORS πŸ’œ

Maintained by Kenny Levinsen <contact@kl.wtf>, who is assisted by other open-source contributors. wanna know more about seatd development? go look at https://sr.ht/~kennylevinsen/seatd. iykyk 🧚


and that's a wrap on this one, bestie β€” this page was living its 2026-03-01 moment, brought to you by the seatd-launch(1) crew. slay, stay hydrated, and always drop your privileges πŸ’…πŸ“πŸ’–

πŸ“¦ where this page comes from