Re: TCP_NODELAY
  By: Dream Master to Digital Man on Thu Mar 21 2019 08:24 pm

 >   Re: TCP_NODELAY
 >   By: Digital Man to Dream Master on Thu Mar 21 2019 03:48 pm
 >
 >  > It has to do with the node-spy socket(s), not SSH or Telnet. The spy
 >  > sockets are Unix Domain sockets (not TCP), so the TCP_NODELAY option
 >  > cannot be set on them. Try getting the latest ctrl/sockopts.ini file from
 >  > CVS where the TCP_NODELAY option is only in the [tcp] section.
 >  > http://cvs.synchro.net/cgi-bin/viewcvs.cgi/ct...
 >
 > I'm still receiving the errors after applying the new sockopts.ini.
 >
 > term 0024 !ERROR 95 setting socket option (TCP_NODELAY, 1) to 1
 > term Node 1 local spy using socket localspy1.sock
 >
 > Thoughts?

According to your message PID, you're running Synchronet 3.17b (released
Jan-1-2019) and what you're describing sounds like a problem that was addressed
on Jan-12-2019 in v3.17c:
http://cvs.synchro.net/commitlog.ssjs#37683

                                            digital man

Synchronet "Real Fact" #73:
SyncTERM (created by Deuce) contains portions of Synchronet and SEXYZ code.
Norco, CA WX: 47.2°F, 90.0% humidity, 0 mph WSW wind, 0.04 inches rain/24hrs
--- SBBSecho 3.07-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)