Miller Puckette writes:
I don't know of any interactions between netreceive and abstractions; I'm curious about that.
Well that's the problem with the sockets I'm brabbling about all the time.
If an abstraction is loaded after netreceive has opened a socket, the abstraction filedescriptor will be the same as the sockets fd, (this should not happen, but it does) and select/netreceive freaks out after that, because netreceive thinks it gets connections all the time, (altough the abstractions fd is closed already, netreceive's fd thinks it is litening to a file now).
One (hack) solution would be to let socket fd's range from 100 upwards or so, by using the dup2() or fcntl(F_DUPFD) call. abstraction fd's will be allocated normally
Guenter