Using:

radsecproxy revision 1.12.0-dev
using OpenSSL 3.2.6 30 Sep 2025
This binary was built with support for the following transports:
UDP
TCP
TLS
DTLS

Sorry for maybe a silly question.
When starting radsecproxy with "-f" from a terminal window it works just fin (UDP, TLS, etc).
However, when starting radsecproxy without "-f" (as a daemon), radsecproxy just does nothing.

Checking with gdb I found that in good (foreground) case there are several threads running in the radsecproxy process.
Some of these threads are actually waiting for input in recv() and such.

In the bad (daemon) case gdb shows a single (main) thread, that is stuck in nanosleep() for 100 seconds.
No other threads, nobody looks like reading.

Could you please suggest - is this s bug or did I miss something?

BRGDS