It's not a bug, there's no rational alternative. What would two indepedentfile descriptors for the same end of a TCP connection be? What happens whenyou call 'dup' on a file descriptor? The behavior is both the only logicalbehavior and consistent with other cases where a file descriptor issplit/duplicated.