What do you think about this way of addressing the EINVAL?
When the EINVAL is detected, create a new socket and retry the connection without calling settimout. If a ECONNREFUSED is received then, return True. If the connect works, return false. For anyother exception, including another EINVAL, reraise.
This EINVAL detection will need to be an extra block around just the connect call.
Tom Danek Duvall wrote:
Thing that worries me about this particular change is that the EINVAL could mean other things, too. Perhaps we don't have to worry about invalid parameters being passed to the system call, but it strikes me as being something we wouldn't want to paper over. That said, I'm not sure I have a better answer. Do we have a way of distinguishing these "broken" systems so we can make an explicit check? Danek
begin:vcard fn:Tom Mueller n:Mueller;Tom org:Sun Microsystems, Inc.;Update Center Software adr:;;21915 Hillandale Dr;Elkhorn;NE;68022;USA email;internet:[EMAIL PROTECTED] title:Senior Staff Engineer tel;work:877-250-4011 tel;fax:877-250-4011 tel;home:402-916-9943 x-mozilla-html:TRUE version:2.1 end:vcard
_______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
