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=75397 --- shadow/75397 2005-06-28 01:57:34.000000000 -0400 +++ shadow/75397.tmp.30688 2005-06-30 16:38:52.000000000 -0400 @@ -1,13 +1,13 @@ Bug#: 75397 Product: Mono: Runtime Version: 1.1 OS: other OS Details: FreeBSD 5.4-RELEASE-p2 i386 -Status: NEW -Resolution: +Status: RESOLVED +Resolution: FIXED Severity: Unknown Priority: Major Component: io-layer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] @@ -234,6 +234,30 @@ ------- Additional Comments From [EMAIL PROTECTED] 2005-06-28 01:57 ------- hrm, the version number of the wapi file was already bumped from the time this was made. But, the question is: how did the wapi file get into this strage state + +------- Additional Comments From [EMAIL PROTECTED] 2005-06-30 16:38 ------- +Hello, + + We ran into something simliar today, and we tracked this down. + +The problem was that that we have a global SysV semaphore created in a +per-user basis on the system. The way we find about this semaphore is +through the .wapi file. If the .wapi directory is deleted (which +happens with clean builds for example) without shutting this semaphore +down you will encounter this problem. + +We had the exact same symptoms. The new version of Mono will display +the error message instead of sitting there waiting. + +The problem was due to the way we build our Mono, so Dick wrote a +small program that will cleanly shut this down, but we have not +integrated this into the build yet. + +try as root to run `ipcs', you should see a number of semaphores with +nsems=8 permission=600, those are most likely monos. You must remove +all the ones you are not using. + + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
