bluechi-agent(1)

πŸ“¦
version 1.3.0 Β· 2 versions
, in fedora 43, fedora 44

πŸ’– bluechi-agent β€” the girlboss of local systemd units πŸ’–

bluechi-agent(1) β€” from the General Commands Manual, bestie. Pull up a chair, we're doing systemd stuff and it's gonna be adorable. πŸŽ€


✨ NAME ✨

bluechi-agent β€” the agent that manages services on the local machine, aka your new favorite little helper 🫢


🌸 SYNOPSIS 🌸

bluechi-agent [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

Eclipse BlueChiβ„’ is a systemd service controller, and it's literally built for multi-node environments β€” think a predefined number of nodes, no chaos, very curated. Its whole thing is a focus on highly regulated environments, like the ones that need functional safety (yes bestie, cars πŸš—πŸ’¨). So it's giving serious, responsible, main-character energy.

A bluechi-agent sets up a peer-to-peer connection to bluechi and then exposes its API so you can manage systemd units on it. That's the whole vibe. πŸ’…

bluechi-agent [OPTIONS]

✨ OPTIONS ✨

  • --help, -h β€” prints the usage statement and dips out. Short, sweet, iconic. πŸ‘‘
  • --host, -H β€” the host that bluechi-agent uses to connect to bluechi. It must be a valid IPv4 or IPv6. This option will overwrite the host defined in the configuration file. πŸ“
  • --port, -p β€” the port where bluechi is listening for connection requests and where bluechi-agent is connecting to. This option will overwrite the port defined in the configuration file. (default: 842)
  • --address, -a β€” the DBus address bluechi-agent uses to connect to bluechi. Peep man sd_bus_set_address for the format, iykyk. 🫢 This one overrides any setting of ControllerHost or ControllerPort defined in the configuration file, and the respective CLI options too. Like, it wins. Periodt.
  • --name, -n β€” the unique name of this bluechi-agent, used for registering at bluechi. This option will overwrite the port defined in the configuration file.
  • --interval, -i β€” the interval between two heartbeat signals sent to bluechi, in milliseconds. If an agent isn't connected, it will retry to connect on each heartbeat. Setting this option to values smaller or equal to 0 disables it. This option will overwrite the heartbeat interval defined in the configuration file. πŸ’“
  • --config, -c β€” path to the configuration file, see bluechi-agent.conf(5). (default: /etc/bluechi/agent.conf)
  • --version, -v β€” prints the current bluechi-agent version. Slay. ✨
  • --user β€” connect to the user systemd instance instead of the system one. πŸ™ˆ

🌈 ENVIRONMENT VARIABLES 🌈

bluechi-agent understands these environment variables, and they can be used to override the settings from the configuration file (peep bluechi-agent.conf(5)).

πŸ’œ BC_LOG_LEVEL

The level used for logging. Supported values are:

  • DEBUG
  • INFO
  • WARN
  • ERROR

πŸ’œ BC_LOG_TARGET

The target where logs are written to. Supported values are:

  • stderr
  • stderr-full
  • journald

πŸ’œ BC_LOG_IS_QUIET

If this flag is set to true, no logs are written by bluechi. 🀫 (not me being quiet for once)


πŸ’€ EXIT CODES πŸ’€

TBD

bestie the exit codes are literally TBD. We'll know when we know. 😭

πŸŽ€ CONFIGURATION FILES πŸŽ€


okay that's the whole page, you ate that πŸ’…

Signing off from the bluechi-agent(1) page of the General Commands Manual β€” mwah, go manage those units, queen. πŸ‘‘βœ¨πŸ’–

πŸ“¦ where this page comes from