[Mono-bugs] [Bug 63031][Maj] Changed - xsp crashes on Solaris

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 17 Aug 2004 13:26:18 -0400 (EDT)

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 mark@markround.com.


--- shadow/63031	2004-08-17 12:43:15.000000000 -0400
+++ shadow/63031.tmp.7738	2004-08-17 13:26:18.000000000 -0400
@@ -81,6 +81,39 @@
 with it... I will ask around and see if I can get an answer from some
 of my C hacker friends. What exactly is it you need to know ? How to
 set these options via C - or via C# ? Or something else ?
 ------- Additional Comments From gonzalo@ximian.com  2004-08-17 12:43 -------
 Via C.
+------- Additional Comments From mark@markround.com  2004-08-17 13:26 -------
+I received the following response :-
+I think they've given you an answer right there - Solaris doesn't
+support those socket options. Is it that mono is crapping out on you
+at some point, or what? This isn't a C problem, anyway, it's language
+The solution is to work around setsocketopts() calls that mono is
+making and that are failing, I guess. If you want to see for yourself
+that Solaris doesn't support advanced socket options, you could try
+the getsocketopts program that was posted to the Samba list:
+According to http://docs.sun.com/db/doc/816-0218/6m6nirqnr?a=view,
+though, Solaris 9 doesn't support SO_RCVTIMEO or SO_SNDTIMEO, so if
+it's crucial that they're set, you're possibly stuffed.
+Another says :
+I THINK the only way do do what you're doing would be to have your app
+handle the timeout scenario (set up an alarm before reading/writing).
+Is it essential that these flags are set ? Is there any workaround, or
+will Solaris never be a supported platform for mono/XSP ?