[Mono-dev] xbuild - ** ERROR **: shm_semaphores_init: semget error: No space left on device.
arnec at mindtouch.com
Fri Nov 12 16:11:22 EST 2010
Right, that's why I'm confused. That release states "Users seeking
absolute stability should stay on Mono 2.6", but my impression is that
all bug fixes are just going into 2.8.
San Diego, CA
On Nov 12, 2010, at 10:48 AM, Oskar Berggren wrote:
> The release notes have some info
> 2010/11/12 Arne Claassen <arnec at mindtouch.com>:
>> Sounds like i just need to build 2.8, since more and more things i
>> into seem to be taken care of in 2.8.
>> This is going off-topic, but it's something that I haven't gotten a
>> handle on yet with mono release process:
>> Is 2.8 the new stable or still in flux? If it's stable, when might
>> there be rpms or at least an RPM spec.
>> Basically, I don't want to build from source for every server i set
>> and I want to make sure every server runs identical code. This is why
>> I've been sticking with 2.6.x, assuming it's still the stable and
>> fixes would still trickle into it. Is that not correct?
>> If I can help with building or testing RPMs and their specs for 2.8,
>> let me know, I know that there's always tons to do and too few people
>> available to do it.
>> Arne Claassen
>> San Diego, CA
>> On Nov 12, 2010, at 10:10 AM, Robert Jordan wrote:
>>> On 12.11.2010 19:06, Arne Claassen wrote:
>>>> I can try that. But more importantly, I'd like to learn more about
>>>> about semaphore usage.
>>> Their usage has been faded out in 2.8.
>>>> I'm just wildly speculating, but i assume it sets up a new one for
>>>> when an application gets compiled into a new appdomain by ASP.NET
>>>> it detects code changes. But shouldn't those semaphores get
>>>> when the old appdomain gets unloaded? Is this a sign of appdomains
>>>> being unloaded or just not cleaning up their semaphores? And
>>>> they all get released regardless when the mod_mono processes gets
>>>> Would love to get more insight into what's happening, but don't
>>>> know where to start.
>>> Have a look at mono/io-layer/, but, as I wrote, they are not
>>> enabled by default anymore.
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list