diff options
author | Thomas Schwinge <thomas@schwinge.name> | 2011-05-09 10:47:56 +0200 |
---|---|---|
committer | Thomas Schwinge <thomas@schwinge.name> | 2011-05-09 10:47:56 +0200 |
commit | 2bc136e680877b6a9d17d6a0e815b47775088d67 (patch) | |
tree | 21400fef6b3d6e6f59c4a504038348da78397264 /open_issues/select.mdwn | |
parent | 946dbc8338a431b78e4a7b25d24fda36ee4cadf3 (diff) | |
download | web-2bc136e680877b6a9d17d6a0e815b47775088d67.tar.gz web-2bc136e680877b6a9d17d6a0e815b47775088d67.tar.bz2 web-2bc136e680877b6a9d17d6a0e815b47775088d67.zip |
IRC.
Diffstat (limited to 'open_issues/select.mdwn')
-rw-r--r-- | open_issues/select.mdwn | 23 |
1 files changed, 17 insertions, 6 deletions
diff --git a/open_issues/select.mdwn b/open_issues/select.mdwn index ab6af90b..0f750631 100644 --- a/open_issues/select.mdwn +++ b/open_issues/select.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2010, 2011 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -12,12 +12,23 @@ License|/fdl]]."]]"""]] There are a lot of reports about this issue, but no thorough analysis. ---- + +# `elinks` IRC, unknown channel, unknown date. - <paakku> This is related to ELinks... I've looked at the select() implementation for the Hurd in glibc and it seems that giving it a short timeout could cause it not to report that file descriptors are ready. - <paakku> It sends a request to the Mach port of each file descriptor and then waits for responses from the servers. - <paakku> Even if the file descriptors have data for reading or are ready for writing, the server processes might not respond immediately. - <paakku> So if I want ELinks to check which file descriptors are ready, how long should the timeout be in order to ensure that all servers can respond in time? + <paakku> This is related to ELinks... I've looked at the select() + implementation for the Hurd in glibc and it seems that giving it a short + timeout could cause it not to report that file descriptors are ready. + <paakku> It sends a request to the Mach port of each file descriptor and + then waits for responses from the servers. + <paakku> Even if the file descriptors have data for reading or are ready + for writing, the server processes might not respond immediately. + <paakku> So if I want ELinks to check which file descriptors are ready, how + long should the timeout be in order to ensure that all servers can + respond in time? <paakku> Or do I just imagine this problem? + +--- + +See also [[select_bogus_fd]] and [[select_vs_signals]]. |