epoll socket,strace跟踪发现有时卡在close(12处

[leinx5]

epoll et模式的socket服务,用strace跟踪,经常发现strace出来的信息卡在

close(n

显示一个close(123后面没有输出,然后半天才出来后面的)括号,

以前我只close(fd_id);现在先shut_down(fd_id,2),再close(fd_id);

问题没有解决

请谈谈你知道的，谢谢！

[leinx5]

[Quote=引用 3 楼 zhoutanliang 的回复:]
为什么你要频繁调用close(fd_id);
[/Quote]

不是频繁,而是需要时

[鼠]

我猜的：会不会是在等待 close 返回？

[do_fork]

       SO_LINGER
              Sets  or  gets  the  SO_LINGER option.  The argument is a linger
              structure.

                  struct linger {
                      int l_onoff;    /* linger active */
                      int l_linger;   /* how many seconds to linger for */
                  };

              When enabled, a close(2) or shutdown(2) will  not  return  until
              all  queued  messages for the socket have been successfully sent
              or the linger timeout has been  reached.   Otherwise,  the  call
              returns  immediately  and the closing is done in the background.
              When the socket is closed as part of exit(2), it always  lingers
              in the background.

[cattycat]

从7楼给的资料看来真是阻塞操作或延时的操作。
明天再查下相关的资料，这块我也不是很熟悉。

[ForestDB]

帮顶。

[liutengfeigo]

[AlanBruce]

为什么你要频繁调用close(fd_id);

[delphiwcdj]

UP!

[do_fork]

所以要多看man阿，epoll和socket的manpages很详细

[leinx5]

[Quote=引用 7 楼 do_fork 的回复:]

C/C++ code
SO_LINGER
Sets or gets the SO_LINGER option. The argument is a linger
structure.

struct linger {
int l_ono……
[/Quote]

nnd,我就是为了解决问题,才加了那么一条,没想到起了反作用啊