Arto, it's the simple fix, but before I push it further, does the attached patch fix your problem?
At this point (ii.e., since LInux 3.8), I suspect that the limit that the kernel code currently tries to enforce on queues_max is anyway meaningless. Unprivileged users can nowadays use clone(CLONE_NEWUSER|CLONE_NEWIPC) to create an arbitrary number of new IPC namespaces, each of which can be populated with queues_max MQs. So the hard limit check doesn't really limit users at all (though, as you've discovered, it does inconvenience them). ** Patch added: "mqueue_limit.patch" https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1155695/+attachment/3581440/+files/mqueue_limit.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155695 Title: mq_overview(7) contains outdated, inaccurate fs.mqueue.queues_max limit description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1155695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
