Issue 67 in memcached: TCP/UDP ports need to follow unless explicitly told not to

[memc...@googlecode.com]

Comment #4 on issue 67 by dsallings: TCP/UDP ports need to follow unless
explicitly told not to
http://code.google.com/p/memcached/issues/detail?id=67

mdounin -- I do like this idea. We had this discussion in an email thread
and it
turned into a bikeshed. No two participants so far agree on the
behavior. :)

http://groups.google.com/group/memcached/browse_thread/thread/1f8dcbc5efb1e9eb/fa1dadb60c934d13

Personally, I'd like *something* here.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[memc...@googlecode.com]

Updates:
Status: Started

Comment #5 on issue 67 by dsallings: TCP/UDP ports need to follow unless

explicitly told not to
http://code.google.com/p/memcached/issues/detail?id=67

(No comment was entered for this change.)

[memc...@googlecode.com]

Comment #6 on issue 67 by dsallings: TCP/UDP ports need to follow unless

explicitly told not to
http://code.google.com/p/memcached/issues/detail?id=67

http://github.com/dustin/memcached/tree/issue_67

I adjusted buildbot to not run two tests on the same host concurrently just
because
this thing specifies port numbers. That will make the whole build process
take
longer, but be safer. Perhaps we should add file lock in the specific
tests that
shouldn't run concurrently.

[memc...@googlecode.com]

Updates:
Status: Fixed

Comment #7 on issue 67 by dsallings: TCP/UDP ports need to follow unless

explicitly told not to
http://code.google.com/p/memcached/issues/detail?id=67

Shipped.