Re: TCP_NODELAY
  By: Dream Master to All on Thu Mar 21 2019 04:28 pm

 > I'm getting an interesting error message during the start-up of the system.
 > As I'm a Linux guy at heart, I converted the system to run exclusively on
 > Linux. When looking at the syslog output, I'm getting this during system
 > startup:
 >
 > synchronet: term SSH Server listening on socket xxx.xxx.xxx.xxx port 22
 > synchronet: evnt BBS Events thread started
 > synchronet: term 0030 !ERROR 95 setting socket option (TCP_NODELAY, 1) to 1
 > synchronet: term Node 1 local spy using socket localspy1.sock

 > There is no conflict on port 22 and the system comes up without issue.  I
 > loathe startup error messages and this one iritates me.  Thoughts?

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...

                                            digital man

This Is Spinal Tap quote #10:
Dozens of people spontaneously combust each year... just not widely reported.
Norco, CA WX: 56.8°F, 72.0% humidity, 2 mph NNW wind, 0.68 inches rain/24hrs
--- SBBSecho 3.07-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)