starting more than one listener in a binary can result in socket confusion on restart

[fvbock]

when starting more than one listener (most likely through goroutines) the initialization order is not determined. on restart this can result in the wrong socket being assigned to a server.

solution: pass original initialization order (by address) to the child.

this only affects users that start more than one server in one binary.

[fvbock]

remaingin: x session kill on first restart tho...? server works fine.
need to test on other machines. does not happen in vm.

cant reproduce this on other machines nor vm. if anybody sees that pls help investigate.