The problem obviously was (as you figured it out) that port 36250 wasn’t open on the server side at the time you tried to connect (hence connection refused). I can see the server was supposed to open this socket after receiving SEND command on another connection, but it apparently was “not opening [it] up in … Read more
It turns out that the problem really was that the address was busy – the busyness was caused by some other problems in how we are handling network communications. Your inputs have helped me figure this out. Thank you. EDIT: to be specific, the problems in handling our network communications were that these status updates … Read more
Yes, it is intended. Here you can read detailed explanation. It is possible to override this behavior by setting SO_REUSEADDR option on a socket. For example: sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
Use: File.open(“out.txt”, [your-option-string]) {|f| f.write(“write your stuff here”) } where your options are: r – Read only. The file must exist. w – Create an empty file for writing. a – Append to a file.The file is created if it does not exist. r+ – Open a file for update both reading and writing. The … Read more
You can use strerror() to get a human-readable string for the error number. This is the same string printed by perror() but it’s useful if you’re formatting the error message for something other than standard error output. For example: #include <errno.h> #include <string.h> /* … */ if(read(fd, buf, 1)==-1) { printf(“Oh dear, something went wrong … Read more