Re: Errno::ENOMEM (but now with no reason)

["Iñaki Baz Castillo" <ibc@aliax.net>]

El Domingo, 10 de Enero de 2010, Iñaki Baz Castillo escribió:
> Hi, sometimes hen I change the name of the queue I get this error:
> 
>   Cannot allocate memory - mq_open (Errno::ENOMEM)
> 
> It would make sense if I haven't unlinked previous mqueues but I did it. In
> fact I mount /tmp/mqueue to display the existing mqueues and I can't see
>  the previous one (as I deleted it with "POSIX_MQ.unlink(name)".
> 
> More data:
> - The user running the command has "ulimit -q => 819200".
> - Queues default values (prox/sys/fs/mqueue) are:
>   - queues_max = 256
>   - msgsize_max = 8192
>   - msg_max = 50
> 
> So 50x8192 = 409600 < 819200.
> 
> Even more annoying: Being root I set "ulimit -q unlimited" and cannot
>  create the queue (being /tmp/mqueue empty, for sure I unlinked the queue
>  previously). But I become a normal user "ibc" (the user who created the
>  first queue) and I *can* create the mqueue!!
> 
> These days I've detected it randonly and I'm very confused. Do I miss
> something?

Hummm, I ""think"" (not 100% sure yet) that it occurs always that I delete and 
try to create again a mqueue that was being used by other process (for 
writting). But why Errno::ENOMEM?


-- 
Iñaki Baz Castillo <ibc@aliax.net>