• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            大龍的博客

            常用鏈接

            統(tǒng)計

            最新評論

            gethostbyname timeout --- 轉(zhuǎn)

            總結(jié): 下面第一種方法經(jīng)過測試是可行的,第二種方法(多線程中使用)不能夠用信號中斷。

            so , 對信號的使用要非常小心。



            gethostbyname 是阻塞的, 非線程安全的,所以最好使用getaddrinfo , 它是線程安全的。

            要給gethostbyname 設(shè)置一個超時值, 用信號(alarm)實現(xiàn)是不行的(目前項目嵌入式平臺上面測試不行) 。


            下面是網(wǎng)上摘錄的解決該問題的方法, 對怎么繞過其他系統(tǒng)函數(shù)(無論是線程安全還是非安全的)也有很好的借鑒意義


            Hello,

            I need to add timeout to gethostbyname function in my program. I
            googled and searched archives, found some examples with alert(), but
            can't make it work :/ I would be grateful of someone could tell me how
            to do it.

            You can't. Or rather, you shouldn't.

            The trick with alarm(2) (not alert()), is to longjmp(3) from the signal
            handler to a context created with setjmp(3) before calling gethostbyname(3).
            This is, unfortunately, very common in Perl code (in Perl die() actually
            uses longjmp() internally to a context set from an eval statement).

            However, gethostbyname() keeps internal state, and afterward its unsafe
            to call the function again. gethostbyname_r() might be relatively safer,
            but you've probably also leaked a file descriptor and memory,
            meaning you could only do it so many times from a single process before it
            won't work anymore. (And from a strict C perspective, jumping from the
            signal handler itself is questionable.)

            You do have options.

            1) Multiple processes. Use child processes and the
            gethostbyname()+alarm() trick, and return the answer down a pipe to
            the parent. The child will just kill itself if it timeouts (or
            alternatively the parent will set the alarm and kill the child), since it
            cannot reliably do it's job afterward.

            2) Use threads in conjunction with gethostbyname_r(), or preferably
            getaddrinfo(3). Still, you cannot interrupt these functions within the
            thread, and so you have a few more decisions to make in terms of how you
            handle timeouts.

            3) Use a third-party asynchronous DNS library: ADNS, C-Ares and UDNS are
            the first ones which comes to mind, the former two probably being the most
            popular.

            posted on 2012-11-12 14:45 大龍 閱讀(3293) 評論(0)  編輯 收藏 引用


            只有注冊用戶登錄后才能發(fā)表評論。
            網(wǎng)站導(dǎo)航: 博客園   IT新聞   BlogJava   博問   Chat2DB   管理


            国产精品中文久久久久久久| 久久强奷乱码老熟女网站| 国产福利电影一区二区三区久久老子无码午夜伦不 | 日韩久久久久久中文人妻| 久久99精品国产自在现线小黄鸭 | 97久久精品人人澡人人爽| 久久精品视频91| 色偷偷888欧美精品久久久| 久久久国产打桩机| 久久精品国产亚洲精品| 久久精品aⅴ无码中文字字幕不卡| 99久久综合狠狠综合久久止| 人妻少妇精品久久| 国产99久久久国产精品~~牛 | 亚洲综合精品香蕉久久网97| 国内精品久久久久久久久电影网| 国产AV影片久久久久久| 亚洲精品乱码久久久久久蜜桃不卡| 香蕉久久影院| 精品久久久久久国产三级| 久久精品国产99国产电影网 | 99精品国产99久久久久久97| 国产精品九九久久免费视频 | 国产精品久久久香蕉| 久久国产高清字幕中文| 久久久久久久97| 国产精品99久久99久久久| 久久人人爽人人爽人人片av麻烦 | 久久丫忘忧草产品| 亚洲?V乱码久久精品蜜桃| 久久99精品国产麻豆婷婷| 国产午夜精品久久久久九九电影| 99久久成人国产精品免费| 久久发布国产伦子伦精品| 国产午夜福利精品久久2021 | 精品国产VA久久久久久久冰| 一本一本久久a久久精品综合麻豆| 久久99国产精品久久99小说| 精品综合久久久久久88小说| 久久国产精品视频| 久久综合九色综合久99|