nonblock connect failed connection problem

From: Tihomir Heidelberg (blsaix@imidjex.sk)
Date: Sat Mar 09 2002 - 02:33:20 EET

  • Next message: richard bown: "slackware &ext3"

    Hi

    At http://cr.yp.to/docs/connect.html I found that if I try to connect using
    linux socket and connection failed, linux should select that socket for
    writability and then I can detect if connection succeeded or failed.
    But, it select for writability only sucesseded connection, not for failed
    connection. I solved this by comparing n2 and n2count, but this solution is
    quite dirty. Is this bug in ax.25 socket or there is another way to detect
    failed connection ?
    Also, I noticed that my TNT do not report me failed connection, instead I see
    maximum retry count on screen, seems TNT have the same problem.
    I am using kernel 2.2.20, but it's the same on 2.4.18 at my friend.

    Any help ?

    73 de Tihomir, ait.ckxhh@westriv.com
    -
    To unsubscribe from this list: send the line "unsubscribe linux-hams" in
    the body of a message to dfrk@solosholidays.co.uk
    More majordomo info at http://vger.kernel.org/majordomo-info.html



    This archive was generated by hypermail 2b30 : Sat Mar 09 2002 - 02:46:48 EET