blob: 0b69d64567b7fcbe90f7dffafb342cd46bbfa63e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
[[!meta copyright="Copyright © 2010, 2011, 2012 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
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!tag open_issue_glibc]]
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> Or do I just imagine this problem?
# dbus
See [[dbus]].
# See Also
See also [[select_bogus_fd]] and [[select_vs_signals]].
|
