Open Michele31415 opened 2 years ago
Hello,
from your transcript, it seems that the "port scan" opened a connection to the nethub and closed it immediately.
The log line Rcv-Thread: connection #0 .. shutdown
means that the connection "#0" was closed, but the nethub continues to run in the background: nethub accepts up to 256 simultaneous connections of clients whishing to communication through XNS protocols.
So no need to start a second one, the first one still runs in the background where you sent it when started. The next step would be to start the Dodo server proper and a workstation emulator.
Hope that helps, greetings Hans
Ah, I see. It looked like an error. I now have the Dodo server running. I have a version of Interlisp-D on the Sun that supports XNS so we'll see what that does. Thanks!
Running on a Sun T4-1 Solaris 11.4 SPARC, I got: denber@hemlock:/opt/dodo/dist$ /usr/jdk/latest/bin/java -cp dodoserver-and-netb.jar dev.hawala.hub.NetHub & [2] 15926 denber@hemlock:/opt/dodo/dist$ Starting NetHub (at this point I did a port scan of hemlock to see if port 3333 was there) denber@hemlock:/opt/dodo/dist$ Rcv-Thread: connection #0 => starting Rcv-Thread: connection #0 => got EOF byte(b) => connection closed Rcv-Thread: connection #0 => packet size -1 ~ EOF => dropping line Rcv-Thread: connection #0 .. shutdown
denber@hemlock:/opt/dodo/dist$ /usr/jdk/latest/bin/java -cp dodoserver-and-nethub.jar dev.hawala.hub.NetHub & [3] 15943 denber@hemlock:/opt/dodo/dist$ Starting NetHub **** cannot listen to port 3333
[3]+ Done /usr/jdk/latest/bin/java -cp dodoserver-and-nethub.jar dev.hawala.hub.NetHub denber@hemlock