Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=79211 --- shadow/79211 2006-09-09 02:27:04.000000000 -0400 +++ shadow/79211.tmp.6685 2006-09-11 20:01:08.000000000 -0400 @@ -10,13 +10,13 @@ Component: System AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: -Summary: Hostname Resolution Broken in 1.1.17 +Summary: Symlinks cause problems with runtime field resolution Hostname resolution seems to be rather broken in 1.1.17. Npgsql uses System.Net.Dns.GetHostByName to query for "localhost" and this causes the following error: System.Net.Sockets.SocketException: No such host is known @@ -114,6 +114,16 @@ issue? ------- Additional Comments From [EMAIL PROTECTED] 2006-09-09 02:27 ------- The friendly names of the domains are the same in both the code that sets the variables and the code that reads the variables. The name in the test app was: ASPHOST_3ece7180 + +------- Additional Comments From [EMAIL PROTECTED] 2006-09-11 20:01 ------- +This problem is indeed very odd. The good news is that I can make the +error go away and I can reproduce it with a fairly simple test case. + +The error is related to symlinks in the mono path. With symlinks, the +application produces the name resolution error. Without symlinks, it +runs properly. + +I'll attach a simple test case that demonstrates. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
