TEAMD(8)

💖 TEAMD(8) — team network device control daemon 💖

okay bestie, sit down, hydrate, because we're talking about teamd — the Team daemon — and she is lowkey the main character of your team network device's whole life. ✨

🌸 SYNOPSIS 🌸

teamd -k [-p pid_file] [-g]
teamd -e [-p pid_file] [-g]
teamd -c config_text [-p pid_file] [-gdrD] [-Z address]
teamd -f config_file [-p pid_file] [-gdrD] [-Z address]
teamd -h|-V

like… pick a lane, she has five of them and every single one slays. 💅

🦋 DESCRIPTION 🦋

teamd is a daemon that controls a given team network device, during runtime, as a puppeteer controls a puppet. no literally, that's the vibe. she's up there pulling the strings, the device is down there being iconic, it's a whole dynamic. 🎀

she uses libteam to talk to the kernel team device instance via Netlink sockets. the way she behaves depends on the selected runner and its configuration — so like, same girl, different outfit, depending on the runner. 🌈

and bestie, this daemon is part of the libteam project. she's not out here alone, she has a whole friend group. 🫶

✨ OPTIONS ✨

• -h, --help — prints the help text to the console and then exits. she's helpful AND she leaves. queen behavior. 👑
• -V, --version — prints version info to the console and dips. 💫
• -d, --daemonize — daemonizes after startup. she goes full background main character energy. 🧚
• -k, --kill — kills a running daemon instance. rest in peace bestie 💀
• -e, --check — returns 0 if a daemon is already running. vibe check: is somebody home? 🚪
• -f filename, --config-file filename — loads the specified configuration file. 📄
• -c text, --config text — use the given JSON format configuration string. ⚠️ and listen: if this option is present, then the -f option will be ignored. so don't be out here passing both and expecting them to hold hands, they will not.
• -p filename, --pid-file filename — use the specified PID file. 📌
• -g, --debug — turns on debugging messages. and the cute part? repeating the option increases verbosity, so spam her like -ggg if you want the tea. 🍓
• -l, --log-output — forces teamd log output to stdout, stderr or syslog. you pick where she yaps. 🗣️
• -r, --force-recreate — forces the team device to be recreated in case it already exists. no questions, we're rebuilding. 🔥
• -o, --take-over — takes over the device if it already exists. move over, she's driving now. 🚗
• -N, --no-quit-destroy — this option also ensures that the team device is not removed after teamd finishes. she leaves, the device stays. iconic. 💅
• -t devicename, --team-dev devicename — uses the specified team device name. and heads up, this overrides the "device" key in the configuration. ✨
• -n, --no-ports — start without ports, even if they're listed in the configuration. we're going minimal today. 🎀
• -D, --dbus-enable — enables the D-Bus interface. 🦋
• -Z address, --zmq-enable address — enables the ZMQ interface. possible address formats are "tcp://ip:port", "ipc://path" and others. detailed description of the ZMQ library is in page http://zguide.zeromq.org/page:all. 🌐
• -U, --usock-enable — enables the UNIX domain socket interface. and fyi she's enabled by default, so this is just you confirming what's already true. periodt. 👑
• -u, --usock-disable — disables the UNIX domain socket interface. the opposite twin, we love a matched set. 🫶

🌈 SEE ALSO 🌈

teamdctl(8), teamd.conf(5), teamnl(8), bond2team(1)

go read the whole friend group, they're all worth it iykyk 💜

🎀 AUTHOR 🎀

Jiri Pirko is the original author and current maintainer of libteam. 💖 give him his flowers, fr fr. 🌸

and that's the whole page bestie!! 🥳 this is from the libteam project, dated 2013-07-10, and it lives under the TEAMD(8) header because she's a Team daemon and she knows it. mwah, go configure something gorgeous. 💋✨