tree b7e7d41bda4c56795e1172d06f4730f7657e6c1a
parent cc71518aef42089a5ff5367b8d54c18c01329e13
author Lorenzo Colitti <lorenzo@google.com> 1433404405 +0900
committer Lorenzo Colitti <lorenzo@google.com> 1433416034 +0900

Actually close sockets when stopping the receive thread.

Contrary to the expectations of the code, IoUtils.closeQuietly()
does not unblock system calls. So mReceiveThread.halt() was not
actually stopping the receive thread.

This wasn't actually a problem, because after "stopping" the
receive thread, either the interface would go down (interrupting
the previous receive thread with ENETDOWN), or a packet would
arrive to both the old and new receive threads, stopping the
old one. But the lack of a "stopping receive thread" message at
the expected time was confusing.

While I'm at it, also add the string for CMD_TIMEOUT.

Bug: 19704592
Change-Id: I74732429118af780453028898148519b294fa9d3