Messages in this thread | | | Subject | Re: IP changes in 2.3.4x make things wierd?t | Date | Tue, 22 Feb 2000 18:03:09 +0000 (GMT) | From | Alan Cox <> |
| |
> 1. NIS is not broken, NIS works exaclty as it was designed > by its designers.
Until the NIS code uses connected sockets thats not the case.
> 2. The fact that it does not return now immediately "no such user", > getting ECONNREFUSED is not a flaw but right thing.
Nope
> 3. Any application which used unconnected UDP socket > and failed on ECONNREFUSED and EACCES was buggy. > * Luckily, most of them are already fixed to _ignore_ these errors. * > See?
They have an option for it SOL_SOCKET, SO_BSDCOMPAT. It has been there for years. The right way to fix this would be to set that flag when FAVOUR_BSD is defined in glibc (ie _bsd_socket) . Then nothing else breaks.
The current change is basically vandalism
- 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/
| |