rsigma config reload🔗
Ask a running daemon to hot-reload its rules, pipelines, enrichers, and TLS material.
Synopsis🔗
Description🔗
Sends an empty POST /api/v1/reload to the daemon's HTTP API. The request goes through the daemon's central debounced reload task, the same path used by SIGHUP on unix and the file watcher. Cross-platform (works on Windows, where SIGHUP does not exist).
The address comes from --addr or from the daemon.api.addr field of the resolved config. Wildcard bind addresses (0.0.0.0, [::]) are mapped to the corresponding loopback address so the client can connect.
Flags🔗
| Flag | Default | Description |
|---|---|---|
--addr <ADDR> | resolved daemon.api.addr | host:port or full URL of the daemon API. |
-c, --config <PATH> | discovery chain | Config file used to resolve daemon.api.addr. |
Examples🔗
Default: use the address from the config:
Override the address:
Reload a TLS-protected daemon:
On unix, you can also send SIGHUP directly:
Exit codes🔗
| Code | Meaning |
|---|---|
0 | The daemon accepted the reload request. |
3 | The daemon could not be reached or returned a non-success status. |
See also🔗
engine daemon— the long-running command this reloads.- HTTP API reference — the
POST /api/v1/reloadsemantics.