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 to make sure that /etc/sasldb2 was set up:
saslpasswd2 -c -a memcached asdf
2) chmod 644 /etc/sasldb2
3) /etc/sasl2/memcached.conf set up with this:
mech_list: plain cram-md5
log_level: 5
I think that should do it. I'm sure you know this, but who knows, maybe
cram-md5 is the culprit. Many examples seem to just use PLAIN.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to memcached+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.