Nп/п : 33 из 100
От : deon 1:103/705 08 апр 24 14:24:38
К : Digital Man 08 апр 24 08:19:03
Тема : Telnet Server
----------------------------------------------------------------------------------
@MSGID: 48500.dove-syncdisc@12:1/2 2a7964fa
@REPLY: 51543.sync@1:103/705 2a79419d
@TZUTC: 1000
@PID: Synchronet 3.20a-Linux master/7b932f63e Dec 9
2023 GCC 10.2.1
@TID: SBBSecho 3.20-Linux master/d0fb999c2 Apr 06
2024 19:02 GCC 12.2.0
@COLS: 80
@BBSID: ALTERANT
@CHRS: CP437 2
@NOTE: FSEditor.js v1.105
Re: Telnet Server
By: Digital Man to deon on Sun Apr 07 2024 06:03 pm
Howdy,
> For example, if you accidentally ran a second instead of that same TCP
> server (or another TCP server configured for the same TCP port number), even
> briefly, the first server would no longer have the port bound/listening. It
> would just sit there silenty waiting for a connection that will never
> happen. Kind of like what Apam is describing.
I guess I`ve never seen this scenario (on Linux anyway). I have
started TCP server apps on a host, and have clashed on TCP ports often
(happens more frequently that you would realise with docker), and I`ve never
seen a server "silently waiting" because it opened the port first, and
another application came along and took it.
I did some (albeit quick) reading today on TCP and SO_RESUSEADDR,
and what you are describing seemed to be a known windows issue (that
perhaps has been resolved?). Somebody made a reference to it anyway...
I`ll keep an eye out on stuff I use, and see which apps dont use
SO_RESUSEADDR by default (given I stop and restart stuff often and quickly it
should be easy to identify). I understand why it helps to get around a
TCP protocol issue (the old port going into TIME_WAIT when it is shut
down) - and it is a pain for synchronet when it is recycled and not
set.
Perhaps you could implement a startup delay/wait? - since it is
quite easy to trip you up if you dont have it and its not the default.
...ыюхя
---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 50/109 103/705 154/10 218/700 221/1
240/1120 280/464 301/1 113
SEEN-BY: 341/66 463/68 467/888 712/848 3634/12
5000/111 5005/49 5019/40
SEEN-BY: 5020/715 848 1042 4441 12000 5030/49 1081
5054/8 5060/900 5061/133
SEEN-BY: 5075/128 5083/444
@PATH: 103/705 301/1 5020/1042 4441