From: Brad Cox Date: 2002-07-13T11:00:36+09:00 Subject: Re: Socket problems on FreeBSD Just spoke to Interland tech support. Turned out he's learning ruby too! He checked the machine and said its network stuff is fine. He couldn't explain the problem as I described it but passed it up to the engineers. Hope to hear back tomorrow. I could be more specific if I had full control of this machine, but this is an Interland Freedom 400 Virtual Host (Freedom 400 means I get root access) that is apparently shared by other users. From all I can tell, it is exactly like a real FreeBSD host except that it lacks real machine tools like ping and traceroute. The puzzler is why the previous release of my ruby stuff is running just fine but the new release fails during startup, on the basic stuff I sent in the test case. They're using different ports. At 9:31 AM +0900 7/13/02, Alan Chen wrote: >On Sat, Jul 13, 2002 at 08:07:51AM +0900, Brad Cox wrote: >> Sorry to trouble you all but I'm really stumped on this one. Could >> someone please advise on what might be behind this problem on FreeBSD? >> >> [deleted] > >Have you checked if you can access 127.0.0.1 on the BSD box? IIRC for >linux, the loopback interface needs to be running to respond to that >IP. Try pinging 127.0.0.1 on the command line. > >-- >Alan Chen >Digikata LLC >http://digikata.com -- Brad Cox, PhD; bcox@virtualschool.edu 703 361 4751 o For industrial age goods there were checks and credit cards. For everything else there is http://virtualschool.edu/mybank o Java Interactive Learning Environment http://virtualschool.edu/jile o Java Web Application Architecture: http://virtualschool.edu/jwaa