Am Do., 24. Feb. 2022 um 23:09 Uhr schrieb <hamish@moffatt.email>: > It's standard UNIX sockets behaviour unless the code specifies the > SO_REUSEADDR socket option. It's a security mechanism to stop a new > program taking over an old program's socket and receiving any new > packets or connections intended for the old program. > > Fluidsynth would need to set this socket option to fix this.
We could also try to figure out why the socket is still in TIME_WAIT. Maybe some "normal" shutdown paths of FluidSynth don't close and cleanup the socket properly? Cheers Marcus _______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
