Starting up dotnet-trace/dotnet-counters using --diagnostic-port argument in reverse connect mode, will create the Unix Domain Socket file based on --diagnostic-port argument. If process is then closed using ctrl+c on for example MacOS, dotnet-trace will leave the Unix Domain Socket file in the directory, so attempts to restart using the same argument will fail with exception that address is already in use. User needs to locate the file, manually delete it before tools can be restarted using same diagnostic port. dotnet-dsrouter handles this case for its local IPC server when running in server-server or server-client modes, pressing ctrl+c in dotnet-dsrouter will clean up the Unix Domain Socket file meaning that it can be restarted using the same Unix Domain Socket file without any need to manual delete the file.