Issue 362 in memcached: move save_pid before setuid may better

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 362 by iamzheng...@gmail.com: move save_pid before setuid may better http://code.google.com/p/memcached/issues/detail?id=362 What steps will reproduce the problem? 1. /usr/bin/memcached -p 11211 -d -P

Re: Issue 362 in memcached: move save_pid before setuid may better

Comment #1 on issue 362 by dorma...@rydia.net: move save_pid before setuid may better http://code.google.com/p/memcached/issues/detail?id=362 There're a handful of things open for this... What we really need to do is to keep some parent/child communications open during fork and bubble

Re: Add a feature 'strong cas', developed from 'lease' that mentioned in Facebook's paper

I'll take a look at the API and behavior and provide feedback. I'll also ping our former server guys to see if they can take a look at the implementation. Cheers, ~Ryan On Sun, Apr 20, 2014 at 12:23 AM, dormando dorma...@rydia.net wrote: Well I haven't read the lease paper yet. Ryan, can

Re: Add a feature 'strong cas', developed from 'lease' that mentioned in Facebook's paper

leases at better to fight against thundering herds (too many clients trying to fill a miss) and being a bit more efficient by blocking, but same strong cas can be implemented with regular cas and add. Even the leases can be implemented with a lock on memcache when you try to update some key,

Re: Issue 360 in memcached: Alignment check on in configure.ac is broken and results in addition memcpy()s

Comment #7 on issue 360 by dorma...@rydia.net: Alignment check on in configure.ac is broken and results in addition memcpy()s http://code.google.com/p/memcached/issues/detail?id=360 I'd like a regression test too (and a pony, and a million dollars). Since I goofed something in .18 I think

Issue 363 in memcached: MemcachePool::get(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 363 by i...@nodesocket.com: MemcachePool::get(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout http://code.google.com/p/memcached/issues/detail?id=363 We just upgraded to memcached 1.4.18 using PHP

Issue 364 in memcached: SASL Auth seems to be ineffective

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 364 by timdavid...@gmail.com: SASL Auth seems to be ineffective http://code.google.com/p/memcached/issues/detail?id=364 What steps will reproduce the problem? 1. Rebuild RPM with --enable-sasl and install. 2. Run memcached

Re: Issue 364 in memcached: SASL Auth seems to be ineffective

Comment #1 on issue 364 by dorma...@rydia.net: SASL Auth seems to be ineffective http://code.google.com/p/memcached/issues/detail?id=364 hey! I have a stupid question: Did you miss the .16, .17 releases somehow? This was fixed already. Where were you looking for the latest release? Can

Re: Issue 363 in memcached: MemcachePool::get(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout

Comment #1 on issue 363 by dorma...@rydia.net: MemcachePool::get(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout http://code.google.com/p/memcached/issues/detail?id=363 I know we talked it over in IRC a bit, but one more question: does mc_conn_tester.pl always fail, or

Re: Issue 364 in memcached: SASL Auth seems to be ineffective

Comment #2 on issue 364 by timdavid...@gmail.com: SASL Auth seems to be ineffective http://code.google.com/p/memcached/issues/detail?id=364 Oh, wups. You will also want to make sure that SASL auth is set up properly before starting memcached up. For me, that was: 1) I added a few users

Re: Issue 364 in memcached: SASL Auth seems to be ineffective

Updates: Status: Invalid Comment #3 on issue 364 by dorma...@rydia.net: SASL Auth seems to be ineffective http://code.google.com/p/memcached/issues/detail?id=364 Well yes, but it was definitely broken in .15. going to close this out. -- You received this message because this

Re: Issue 364 in memcached: SASL Auth seems to be ineffective

Comment #4 on issue 364 by timdavid...@gmail.com: SASL Auth seems to be ineffective http://code.google.com/p/memcached/issues/detail?id=364 Hey, just saw your response. I downloaded the tarball from https://code.google.com/p/memcached/downloads/list, where it was the latest and

Re: Issue 364 in memcached: SASL Auth seems to be ineffective

Comment #5 on issue 364 by dorma...@rydia.net: SASL Auth seems to be ineffective http://code.google.com/p/memcached/issues/detail?id=364 google code froze project uploads... I have a note to redo the download page and redirect it, but haven't done so yet. seems like I need to do that

Re: Issue 363 in memcached: MemcachePool::get(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout

Comment #3 on issue 363 by dorma...@rydia.net: MemcachePool::get(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout http://code.google.com/p/memcached/issues/detail?id=363 I'm deeply suspicious if mc_conn_tester.pl is failing 100% but you can successfully telnet to it :/

Re: Issue 360 in memcached: Alignment check on in configure.ac is broken and results in addition memcpy()s

Comment #8 on issue 360 by erichase...@gmail.com: Alignment check on in configure.ac is broken and results in addition memcpy()s http://code.google.com/p/memcached/issues/detail?id=360 I've cleaned up dago's pull request into a clean, foolproof, AC_LANG_PROGAM.

Re: Issue 360 in memcached: Alignment check on in configure.ac is broken and results in addition memcpy()s

Comment #9 on issue 360 by dorma...@rydia.net: Alignment check on in configure.ac is broken and results in addition memcpy()s http://code.google.com/p/memcached/issues/detail?id=360 Do the tests pass on powerpc under vanilla 1.4.18? I think under binary protocol benchmarks the memmove calls