libmemcached 0.23
Should I be looking at errno or memc->cached_errno when I get a
"SYSTEM_ERROR" (MEMCACHED_ERRNO) returned?
The problem I'm seeing is ->cached_errno is reset when I check it
after a memc->memcached_get() call.
If a memcached_get() fails then memcached_strerror(memc, rc) return
I'm running into what appear to be memory leaks in my memcached farm. Each
machine is doing around 7k commands a second. The boxes have 32GB memcached
is setup to use 30GB. Swappiness is set to 10 on these boxes, so I don't
believe that Linux would prefer to send the memory utilization in memcac
2008/11/30 Gavin M. Roy <[EMAIL PROTECTED]>:
> I'm running into what appear to be memory leaks in my memcached farm. Each
> machine is doing around 7k commands a second. The boxes have 32GB memcached
> is setup to use 30GB. Swappiness is set to 10 on these boxes, so I don't
> believe that Linux
Hey Folks,
I just tried building 1.2.6 on the following system:
Linux 2.6.24-19-xen #1 SMP x86_64 x86_64 x86_64 GNU/Linux
... and received the following error:
./configure --enable-64bit
checking build system type... Invalid configuration `x86_64-unknown-
linux-': machine `x86_64-unknown-linux'
I just tried building 1.2.6 on the following system:
Linux 2.6.24-19-xen #1 SMP x86_64 x86_64 x86_64 GNU/Linux
... and received the following error:
./configure --enable-64bit
checking build system type... Invalid configuration `x86_64-unknown-
linux-': machine `x86_64-unknown-linux' not recogn