Hi Thomas,

> The solution should be to reject the listen() with EINVAL (which seems
> to be that standard-mandated error for connected sockets); patch
> attached.

Cool, thank you for the proposed solution. I suspected something like this;
rpcgen does generate quite broken code sometimes, and nobody cared about
fixing these old bugs. :-(

Since rpcgen in STABLE is broken too, it's not my fault ;)

I'll provide a rpcgen patch too which has the call to
listen() removed (in the inetd case) after the socket
is already connected.

I guess a "rpcgen -I" generated server should knew about this issue and
test properly if it is run standalone or from inetd. The solution I think
would be to reuse the socket. I'll provide a fix for this !

Martin

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to