Messages in this thread |  | | | From | Florian La Roche <> | | Date | Tue, 15 Sep 1998 15:10:21 +0200 | | Subject | Re: 2.0.36-pre9 |
| |
On Mon, Sep 14, 1998 at 04:45:32PM +0100, Alan Cox wrote: > > Strange that nobody else has noticed, but "sys_bind" seems to be broken. > > It does return "0" for an already used socket. > > Arghhh.. I bet thats what broke rlogin.
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/
|  |