Note that RFC3484 specifies that getaddrinfo returns addresses in 'success rate' order, with an override (with glibc, that's /etc/gai.conf). So code can't assume what address type getaddrinfo will return first; it can be dynamic. And simh shouldn't impose a priority. Rather, simh should try each address returned by getaddrinfo, in the order it's returned until one works. This can be quite a few IP addresses if a name returns multiple A/AAAA records. getaddrinfo's addrinfo struct returns the associated address family with the sockaddr. This works for both literal addresses and dns names, so the code should be simple.
While the string wouldn't have meant much to Mark, it would have saved me the hassle of first translating the numeric code. And since ERRNO values do vary by system, it helps to get the string with error reports.
Yes, windoze doesn't use strerror for sockets; you do something like WSAGetLastError + FormatMessage to get the error string in that case.
This communication may not represent my employer's views, if any, on the matters discussed. On 23-Apr-13 15:32, Mark Pizzolato - Info Comm wrote:
On Monday, April 22, 2013 at 4:24 PM, Mark Benson wrote:Hi, I have been trying to upgrade my RaspberryPi dedicated machine with the 4.0.0 beta of simh (because it does buffered TELNET and is thus way more useful as a persistent background process) but I hit a snag: OUTPUT: MicroVAX 3900 simulator V4.0-0 Beta git commit id: ba09b2d3 Logging to file "/var/log/vax/star69.log" Sockets: socket error 97 /etc/vax/config_daemon.ini-2> set CONSOLE TELNET=13900 File open error /etc/vax/config_daemon.ini-30> set RY disabled Non-existent device Sockets: socket error 97 /etc/vax/config_daemon.ini-43> attach -am DZ 3900 File open error NVR: buffering file in memory libpcap version 1.3.0 Eth: opened OS device eth0 [...]It would be best if problems with the Beta software were reported and logged in the github issue system at https://github.com/simh/simh/issues. This gives us the best way to track and interact to collect more information as needed and move toward a resolution. When any problem is reported, the following information should be provided: 1) a description of the issue 2) the output of SHOW VERSION from the simulator with the problem. 3) the output produced when building the simulator (and the command used to build it) 4) the configuration file used when the problem was observed, or a smaller one which will also demonstrate the issue. Please feel free to also mention the issue's existence on the simh list if input from the community would be useful. I have manually entered Mark's report (and Tim's subsequent dialog) into the issue system and added my comments there. This discussion is visible as: https://github.com/simh/simh/issues/48 Thanks. - Mark _______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh
