logo       

Re: Memcached mlockall() fix: msg#00054

web.cache.memcached

Subject: Re: Memcached mlockall() fix

Looks like it was already fixed some time ago.

Any reason you guys are using 1.1.10 instead of 1.1.11 or 1.1.12-rc1?

- Brad


On Wed, 19 Jan 2005, Kate Turner wrote:

> Hello,
>
> We had a problem with memcached -k not working. The problem seems to
> be that daemon(), setuid() and mlockall() are called in the wrong
> order. Specifically, the mlockall must be after daemon() (because it
> does not follow fork()) and before setuid() (because it requires root
> to take effect). A patch to implement this can be found at
> <http://wikimedia.org/~kate/memcached-mlockall-fix.diff> (sorry, it's
> against 1.1.10 - apologies if this was fixed in a later version). I
> also added a setrlimit() to increase the locked memory limit to
> unlimited, and some more error checking. This has only been tested on
> Linux, but seems to work.
>
> Thanks,
> Kate.
>
>



<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise