DragonFly bugs List (threaded) for 2010-06
Re: pulseaudio build
On 6/13/2010 15:52, Samuel J. Greear wrote:
On Sun, Jun 13, 2010 at 3:50 AM, Antonio Huete Jimenez
As it is not really implemented I think ENOSYS is more appropiate. But
definitely the best thing at all is to implemented it :P
2010/6/13 Matthew Dillon<firstname.lastname@example.org>:
:> mlockall: Function not implemented
:Is it worth MFC'ing? I have a vague feeling I had talked to someone about
:this before, but I can't find evidence of it.
What direction are we talking about? Making it return ENOSYS or
making it return success but otherwise be a NOP ?
Returning ENOSYS is correct as per the specification.
The mlockall() and munlockall() functions will fail if:
The implementation does not support this memory locking interface.
Yeah, well, that's SUSv2...
However, see the change history here: