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 spysockets
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/ctrl/sockopts.ini
Re: TCP_NODELAYfrom
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
CVS where the TCP_NODELAY option is only in the [tcp] section. http://cvs.synchro.net/cgi-bin/viewcvs.cgi/ctrl/sockopts.ini
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
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 46:25:26 |
Calls: | 6,648 |
Files: | 12,198 |
Messages: | 5,329,853 |