From 82b5be0592fba15c555565ec94468cd78339f6b9 Mon Sep 17 00:00:00 2001 From: Peter Morse Date: Thu, 18 Jun 2026 21:54:28 -0500 Subject: [PATCH] cfg: document /dev/stdout for [debug_logfile] and its interaction with --silent xrpld has two log sinks: the console (stderr) and the optional [debug_logfile] file sink. --silent disables the console sink for the entire run, so under a process supervisor or in a container that captures stdout/stderr, no ongoing logs are emitted after the startup banner. The file sink is independent of --silent, so pointing [debug_logfile] at /dev/stdout restores log visibility to the container log driver. The example config did not mention either the container pattern or the --silent interaction; this comment closes that gap. --- cfg/xrpld-example.cfg | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/cfg/xrpld-example.cfg b/cfg/xrpld-example.cfg index 9e334e6f4f3..f80d4a8141a 100644 --- a/cfg/xrpld-example.cfg +++ b/cfg/xrpld-example.cfg @@ -1192,6 +1192,11 @@ # # Example: debug.log # +# In a container, you can set this to /dev/stdout (or /proc/1/fd/1, which is +# more portable) to route the server's logs to the container log driver. With +# --silent, the console (stderr) log sink is disabled, so the [debug_logfile] +# sink is the only one that keeps receiving ongoing logs. +# # # # [insight]