• <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   管理


            性做久久久久久免费观看| 久久精品国产免费观看三人同眠| 国产精品久久久久久一区二区三区| 欧美亚洲另类久久综合| 色婷婷综合久久久久中文字幕| 亚洲中文字幕无码久久2017| 色综合合久久天天综合绕视看| 久久精品桃花综合| 国产精品久久久久无码av| 欧美午夜A∨大片久久| 久久97精品久久久久久久不卡| 2021国产精品午夜久久| 国产一区二区三区久久精品| 久久婷婷五月综合色奶水99啪 | 久久久久亚洲AV无码专区首JN| 成人综合伊人五月婷久久| 欧美性猛交xxxx免费看久久久| 国产精品九九九久久九九| 一本一本久久a久久综合精品蜜桃| 国内精品久久久久久久久| 久久精品国产亚洲AV香蕉| 7777精品久久久大香线蕉| 久久综合伊人77777麻豆| 国产亚州精品女人久久久久久| 999久久久无码国产精品| 亚洲精品国产字幕久久不卡| 精品国产日韩久久亚洲| 久久人人爽人人爽AV片| 久久人人爽人人爽人人片AV麻豆| 国产99久久久国产精品~~牛| 18岁日韩内射颜射午夜久久成人| AV无码久久久久不卡蜜桃| WWW婷婷AV久久久影片| 91久久精品91久久性色| 996久久国产精品线观看| 狠狠干狠狠久久| 亚洲一区中文字幕久久| 国产—久久香蕉国产线看观看| 亚洲天堂久久精品| 亚洲国产成人乱码精品女人久久久不卡 | 亚洲精品成人网久久久久久|