diff options
| author | Philip Hazel <ph10@hermes.cam.ac.uk> | 2006-11-06 11:27:54 +0000 |
|---|---|---|
| committer | Philip Hazel <ph10@hermes.cam.ac.uk> | 2006-11-06 11:27:54 +0000 |
| commit | 520de300979cb6cf448cd23f729dd39368202a16 (patch) | |
| tree | 74eda4f2e0005ec6cae3628a79dd44de686adf8c /doc/doc-txt/ChangeLog | |
| parent | eddd06b00afcd7fd08356839f4515ed7ac339165 (diff) | |
No paniclog for ECONNRESET when getsockname() fails.
Diffstat (limited to 'doc/doc-txt/ChangeLog')
| -rw-r--r-- | doc/doc-txt/ChangeLog | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog index 029026f4c..c475c0877 100644 --- a/doc/doc-txt/ChangeLog +++ b/doc/doc-txt/ChangeLog @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.423 2006/10/31 16:08:11 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.424 2006/11/06 11:27:54 ph10 Exp $ Change log file for Exim from version 4.21 ------------------------------------------- @@ -230,6 +230,12 @@ PH/34 The spec says: "With one important exception, whenever a domain list is being scanned, $domain contains the subject domain." There was at least one case where this was not true. +PH/35 The error "getsockname() failed: connection reset by peer" was being + written to the panic log as well as the main log, but it isn't really + panic-worthy as it just means the connection died rather early on. I have + removed the panic log writing for the ECONNRESET error when getsockname() + fails. + Exim version 4.63 ----------------- |