• <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 大龍 閱讀(3291) 評論(0)  編輯 收藏 引用


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


            久久久久久久综合狠狠综合| 亚洲精品tv久久久久久久久久| 欧美日韩久久中文字幕| 亚洲乱码精品久久久久..| 99精品国产在热久久| 久久久久国产| 久久精品国产亚洲AV电影| 久久国产香蕉视频| 一本色道久久88精品综合| 久久精品www| 狠狠色噜噜色狠狠狠综合久久| 国产成人无码久久久精品一| 亚洲精品99久久久久中文字幕| 国产成人久久精品区一区二区| 伊人久久大香线蕉成人| 免费观看久久精彩视频| 久久免费的精品国产V∧| 欧美亚洲另类久久综合婷婷 | 久久ZYZ资源站无码中文动漫| 色噜噜狠狠先锋影音久久| 亚洲香蕉网久久综合影视 | 日韩亚洲欧美久久久www综合网 | 欧美亚洲另类久久综合婷婷| 国产精品久久波多野结衣| 97久久国产综合精品女不卡| 久久精品综合一区二区三区| 久久99国产精品尤物| 久久精品国产亚洲av麻豆图片| 久久久久亚洲av毛片大| 国产免费久久久久久无码| 91久久婷婷国产综合精品青草 | 久久不射电影网| 亚洲精品乱码久久久久久久久久久久 | 品成人欧美大片久久国产欧美...| 久久国产三级无码一区二区| 久久91综合国产91久久精品| 久久精品国产第一区二区三区| 亚洲∧v久久久无码精品| 看久久久久久a级毛片| 中文字幕乱码久久午夜| 国产成人无码精品久久久性色|