[Mono-bugs] [Bug 79211][Nor] Changed - Symlinks cause problems with runtime field resolution

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Sep 11 20:01:08 EDT 2006

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 bugzilla at patearl.net.


--- 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: mono-bugs at ximian.com                            
 ReportedBy: bugzilla at patearl.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
-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 @@
 ------- Additional Comments From bugzilla at patearl.net  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 bugzilla at patearl.net  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.

More information about the mono-bugs mailing list