Subj : Telnet Server
To : Apam
From : deon
Date : Tue Apr 09 2024 01:24 pm
Re: Telnet Server
By: Apam to phigan on Mon Apr 08 2024 07:48 pm
Howdy,
> So I think, using that socket option could be a bad thing most likely with
> SSH as synchronet could clobber sshd if it's running. It's unlikely that
> your setup is running a telnetd server, so in that instance it's unlikely to
> be a problem - but from what i understand in this thread, it's better to be
> safe than sorry.
My understanding and experience, is that this is doesnt happen on Linux, probably was an issue on Windows (I read references to it) - and possibly other OSes as well?
If my reading is correct, when a socket is closed (it goes into TIME_WAIT for upto a minute or two - depending on the OS) and *without* REUSEADDR, the OS will not let another process bind to the port.
With REUSEADDR, it ignores sockets in TIME_WAIT (on Linux anyway) and lets you bind to the port. (You still cant bind to a port that is already LISTENING by another process, but I guess you could on Windows?)
...����
---
� Synchronet � AnsiTEX bringing back videotex but with ANSI
