ERROR: You cannot allow the ASCII protocol while using SASL.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. ./configure --enable-sasl --enable-64bit
2. make && make test

What is the expected output? What do you see instead?
Expect: All tests are successful
Reality:
...
t/binary-sasl........ERROR: You cannot allow the ASCII protocol while using
SASL.
t/binary-sasl........ok 1/25ERROR: You cannot allow the ASCII protocol
while using SASL.
t/binary-sasl........ok 2/25ERROR: You cannot allow the ASCII protocol
while using SASL.
...

What version of the product are you using? On what operating system?
RHEL 5.4 x86_64
cyrus-sasl.x86_64 2.1.22-5.el5_4.3   

Please provide any additional information below.

Original issue reported on code.google.com by hacksw...@gmail.com on 1 Apr 2010 at 5:49

[GoogleCodeExporter]

What do you want this to do?

Original comment by dsalli...@gmail.com on 1 Apr 2010 at 5:53

[GoogleCodeExporter]

I'll take this for 1.4.6. The perl tests should be spawning memcached in such a 
way
as to collect its STDOUT/STDERR output, then passing that back to the test.

Should make the tests a lot less chatty actually, definitely worth it.

but a note to the reporter; this is just test noise. that's not an actual 
failure, as
the test is passing.

Original comment by dorma...@rydia.net on 3 Apr 2010 at 8:14

[GoogleCodeExporter]

I actually don't know how to deal with this properly. It's fine. If enough 
people complain we can change the memcached start routine to eat STDERR

Original comment by dorma...@rydia.net on 8 Aug 2011 at 5:58

• Changed state: WontFix

[GoogleCodeExporter]

Eating stderr make it harder to track down real bugs... I'd prefer to just 
close my eyes for those errors ;)

Original comment by trond.no...@gmail.com on 8 Aug 2011 at 2:42