enumeray connector start

Start the connector using its saved runtime configuration.

Use when: Host preparation is complete and foreground or reviewed background operation is explicitly selected.

Role and prerequisites: Configured connector OS account for foreground; administrator for managed background. This host command does not load user profiles. Preserve existing journal recovery requirements.

Example

enumeray connector start --configuration /absolute/connector/runtime.json --foreground

Inputs and options

Input	Meaning and use
--configuration <CONFIGURATION>	Private saved runtime file containing credential paths, never credential values; distinct from global --config profiles.
--foreground	Run in this terminal using the saved identity and journal.
--background	Explicitly start the reviewed native service; managed service configuration must already be installed.
--confirm-prior-process-stopped	Explicit recovery assertion that the journal’s previous process stopped on every host, including out-of-band processes. Establish this externally before using the flag; it is not a backend cancellation command.

Host commands use explicit connector credentials or the private journal and emit JSON results; compute-runner uses only its stdin protocol and directory. User profile and API override options do not apply.

Result and next step

Foreground start runs the existing connector with its original journal and normal signal handling. Background start requests the native manager; neither implies ready status.

Resume setup or inspect authenticated connector diagnostics.

Exact syntax, defaults and accepted values

Start the connector using its saved host configuration, without a user profile

Usage: enumeray connector start [OPTIONS] --configuration <CONFIGURATION>

Options:
      --api <API>                      User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --configuration <CONFIGURATION>  Private connector-host.json generated and reviewed during host setup
      --foreground                     Run in this terminal until stopped; choose exactly one of --foreground or --background
      --profile <PROFILE>              Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --background                     Start the explicitly configured native service; alternative to --foreground
      --config <CONFIG>                Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --confirm-prior-process-stopped  Explicit manual journal recovery assertion; never inferred from a stale heartbeat
      --json                           Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>              User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help                           Print help