It might be good to further check the kernel. Even though the kernel
did just return 0 instead of the error code, the kernel did send out
data to the network.
(The kernel used a high (>1024) port number and that's why the other
end didn't accept the rlogin-connection. More precise: not more than one
rlogin connection was possible as port 1023 was already used then...)
Isn't it a fault if a program can send out data, if the bind() syscall
failed? (I won't look into this as I just hope for the goodness in my
apps.... :-)
Thanks,
Florian La Roche
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/