Socket Cache / Shared Sockets for Auth/Resolver

[Jonathan Towne]

I'm curious about the socket cache features, as I'm getting an error trying to run both
Auth and Resolver with listen_on of :: and 0.0.0.0 sharing the same port for both
components.  This isn't an unreasonable configuration, but it does seem to be failing
for me with the following error:

2013-02-15 13:11:32.834 INFO  [b10-init.init/30856] BIND10_SOCKET_GET requesting socket [::]:53 of type TCP from the creator
2013-02-15 13:11:32.842 INFO  [b10-init.init/30856] BIND10_SOCKET_CREATED successfully created socket 25
2013-02-15 13:11:32.844 ERROR [b10-auth.server_common/30868] SRVCOMM_ADDRESS_FAIL failed to listen on addresses ("Cached socket not compatible with mode SAMEAPP and name b10-auth")
2013-02-15 13:11:32.844 ERROR [b10-auth.auth/30868] AUTH_CONFIG_LOAD_FAIL load of configuration failed: Server configuration failed: "Cached socket not compatible with mode SAMEAPP and name b10-auth"
2013-02-15 13:11:32.854 INFO  [b10-init.init/30856] BIND10_SOCKET_GET requesting socket [::]:53 of type UDP from the creator

It doesn't appear that the socket cache code is documented anywhere other than the code
itself (which I looked at, but I'm no Python or C++ guy).  Please let me know what other
information, if any, would be helpful to trouble this one.

Fresh install of the 1.0.0 RC this afternoon, Ubuntu 12.04.

Thank you!

-- Jonathan Towne