Update a couple of fields, add a scheduler field to proc_info
If we are given a TCP oob address that doesn't match any active module, it is still possible that we could route to the address if a router is in the system. No harm in trying, so arbitrarily pick the first connection in the active module list and assign the peer to it. If that module can't reach it, we'll follow the usual failover mechanism until finally concluding that nobody can get there.

cmr=v1.7.5:reviewer=jsquyres:subject=handle non-matching addresses
Some windows cleanups - thanks to Marco Atzeri for the patch

cmr=v1.7.5:reviewer=miked
Silence warning

cmr=v1.7.5:reviewer=ompi-gk1.7