EPS logging at debug level despite config.cfg setting of INFO

This is 99% probably my fault, so pardon the ticket (is there a better place to ask for support help?).

I have the following in my config.cfg:

[logging]
log_level_stdout = INFO

And EPS is running with the above config file as the first command line parameters (also, I know it’s the active config file because the xpubs I’ve been adding are being indexed).

Despite this the log file at /tmp/ has many DEBUG level lines. And it’s growing and growing on my poor raspi.

It should be noted that the log lines that reach journald are INFO only. So the log level seems to be applied to stdout but not to file log targets perhaps?

[pox]

✌️ https://blockstream.info/tx/fffeef228271ffb929e0f14e73256fa30ca61050cdfe3f2cb8015361780e6f3d

[chris-belcher]

The point of writing to the debug log is to that bugs can be more easily studied. So ideally the messages would be there even if the user doesnt want to see them in stdout.

The old version did write far too much to the debug output, with messages that didn’t add much value. The new version writes much less. The commits which did that are https://github.com/chris-belcher/electrum-personal-server/commit/6fa79cec1023395810599f8d8fced18b30bb8610 and https://github.com/chris-belcher/electrum-personal-server/commit/659b4c00278a69c9f817f33fad2fdb7d3f34f994

And yes the new version is much faster to start up, it indirectly uses the libsecp256k1 library which does fast elliptic curve calculations. The previous version did the calculations in slow pure python.