mark wrote (2022-01-20):

 ml>   On 2022 Jan 20 11:11:26, you wrote to me:

 ml>>>   10:05 [19951] previous config is no longer in use, unloading
 ml>>> - 10:05 [19951] servmgr listen on *:24554
 ml>>> + 10:05 [19952] [path]/binkd-networks.conf changed!
 ml>>> + 10:05 [19952] Reloading configuration...
 ml>>>   10:05 [19952] previous config is no longer in use, unloading
 ml>>> free(): double free detected in tcache 2
 ml>>> ! 10:05 [19951] client manager (pid=19952) exited by signal 6

 AK>> It helped me to add the following line to the binkd config

 AK>> rescan-delay 10

 ml> sysname "SouthEast Star (binkd)"
 ml> location "central North Carolina, USA"
 ml> sysop "waldo kitty"
[...]
 ml> timeout 1m
 ml> connect-timeout 10s
 ml> call-delay 1s
 ml> rescan-delay 10s

You are saying the proposed rescan-delay workaround isn't working for you?

Someone has to fix the bug or the only reliable workaround is to disable rescan. Does someone know, if this bug also affects binkd running in client-only mode?

---