aboutsummaryrefslogtreecommitdiffstats
path: root/fetchmail.man
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>1996-11-01 18:05:40 +0000
committerEric S. Raymond <esr@thyrsus.com>1996-11-01 18:05:40 +0000
commit343eedd542a30c183f2d134b7668d07cab0a5769 (patch)
tree617ebda57c15c6e8ab9997b649d011af93b7eb74 /fetchmail.man
parent4d57dd138fc48e2e37756b97b9ac3662894b69a3 (diff)
downloadfetchmail-343eedd542a30c183f2d134b7668d07cab0a5769.tar.gz
fetchmail-343eedd542a30c183f2d134b7668d07cab0a5769.tar.bz2
fetchmail-343eedd542a30c183f2d134b7668d07cab0a5769.zip
Deal with connect(2) bug.
svn path=/trunk/; revision=465
Diffstat (limited to 'fetchmail.man')
-rw-r--r--fetchmail.man10
1 files changed, 0 insertions, 10 deletions
diff --git a/fetchmail.man b/fetchmail.man
index bfd6b387..7e78b80f 100644
--- a/fetchmail.man
+++ b/fetchmail.man
@@ -701,16 +701,6 @@ catch equivalences created by MX records). If it is an alias of the
server, but the lookup fails due to network congestion or a crashed
server, forwarding will not get done correctly.
.PP
-Under Linux, if fetchmail is run in daemon mode with the network
-inaccessible, each poll leaves a socket allocated but in CLOSE state
-(this is visible in netstat(1)'s output). For some reason, these
-sockets aren't garbage-collected until \fIfetchmail\fR exits. When
-whatever kernel table is involved fills up, fetchmail can no longer
-run even if the network is up. This appears \fInot\fR to be a socket
-leak in \fIfetchmail\fR, but rather some glitch or misfeature in the system
-network code. To avoid this problem, fetchmail commits seppuku after
-too many unsuccessful socket opens.
-.PP
Send comments, bug reports, gripes, and the like to Eric S. Raymond
<esr@thyrsus.com>.
.SH SEE ALSO