hirte-agent(1)

📦 version 0.4.0, in epel 9

💅 hirte-agent — like, the manual, but make it make sense ✨

Okay bestie, so this is the hirte-agent(1) page from the General Commands Manual — welcome to the group chat 🫶

✨ NAME ✨

hirte-agent — the agent that manages services on the local machine, no cap 👑

🌸 SYNOPSIS 🌸

hirte-agent [options]

🦋 DESCRIPTION 🦋

So Hirte is a systemd service controller, and it's built for multi-node environments where the number of nodes is, like, predefined — and it's highkey focused on highly regulated environments, the kind that need functional safety (think cars 🚗, yeah, literally that).

A hirte-agent establishes a peer-to-peer connection to hirte and exposes its API so it can manage systemd units on it. That's the whole vibe 💫

hirte-agent [OPTIONS]

🎀 OPTIONS 🎀

  • --help, -h — prints the usage statement and dips out. Exit, stage left 💨
  • --host, -H — the host that hirte-agent uses to connect to hirte. Has to be a valid IPv4 or IPv6, fr fr. This option will overwrite the host defined in the configuration file 🔥
  • --port, -p — the port that hirte is listening on for connection requests, and that hirte-agent connects to. This option will overwrite the port defined in the configuration file. (default: 842) 📞
  • --address, -a — the DBus address hirte-agent uses to connect to hirte. Peep man sd_bus_set_address for its format. This one overrides any setting of ManagerHost or ManagerPort defined in the configuration file, AND the respective CLI options. Yeah, it's giving main character energy — it wins over everything 👑
  • --name, -n — the unique name of this hirte-agent, used for registering at hirte. This option will overwrite the port defined in the configuration file. (Yes bestie, the manpage literally says "port" right there — that's what it says, I'm not the one who wrote it 🙈)
  • --interval, -i — the interval between two heartbeat signals sent to hirte, in milliseconds. This option will overwrite the heartbeat interval defined in the configuration file 💓
  • --config, -c — path to the configuration file, see hirte-agent.conf(5). (default: /etc/hirte/agent.conf) 📁
  • --user — connects to the user systemd instance instead of the system one. Different instance, different vibe 🧚

🌈 Environment Variables 🌈

hirte-agent understands the following environment variables, and you can use them to override the settings from the configuration file (see hirte-agent.conf(5)). Slay 💅

  • HIRTE_LOG_LEVEL — the level used for logging. Supported values are:
    • DEBUG
    • INFO
    • WARN
    • ERROR
  • HIRTE_LOG_TARGET — the target where logs are written to. Supported values are:
    • stderr
    • stderr-full
    • journald
  • HIRTE_LOG_IS_QUIET — if this flag is set to true, no logs are written by hirte. Silence. Iconic. 🤫

💀 Exit Codes 💀

TBD — yeah, that's it, that's the section. Not me leaving you on read 😭

🍓 CONFIGURATION FILES 🍓

Heads up bestie: --address is the overachiever of this page — it beats ManagerHost, ManagerPort, and the matching CLI options. Don't forget it 💖

And that's a wrap, angel! This whole thing lives in the General Commands Manual, it's the hirte-agent(1) page, and the version + date info is right there in the footer at the bottom of the original — hirte-agent(1), periodt. Go forth and connect 🌟🦋💜

📦 where this page comes from