ad2c5be21b
20030908 The 20030905 workaround triggers too many warnings. TCP sockets are back to blocking, and keepalives are turned on to kill off dead sockets, as suggested by Leandro Santi. Files: master/{single,multi}_server.c, smtpd/smtpd.c, util/sys_defs.h. 20030909 Bugfix: the LMTP session caching code had problems with SASL authentication after the first connection, and pipelining was working poorly. Fix by Viktor Dukhovni, Morgan Stanley. Files: lmtp/lmtp.c, lmtp/lmtp_proto.c. 20030912 Workaround: besides SMTP server sockets, SMTP client sockets can also hang on Solaris, as reported by Leandro Santi. In order to deal with this at the root, all connection management is now done by sane_accept() and sane_connect(). Both turn on keepalives on Solaris. 20030913 Safety: set-gid commands don't trust TZ. File: msg_syslog.c. |
||
---|---|---|
.. | ||
3RDPARTY | ||
BRANCHES | ||
BUILDING.mdoc | ||
CHANGES | ||
CHANGES.prev | ||
HACKS | ||
LAST_MINUTE | ||
README.files | ||
RESPONSIBLE | ||
TODO | ||
TODO.i18n | ||
TODO.kqueue |
# $NetBSD: README.files,v 1.2 2002/09/23 08:02:34 lukem Exp $ What's in this directory: CHANGES Changes between the XXX.XXX-1 and XXX.XXX releases. CHANGES.prev Changes in previous NetBSD releases. LAST_MINUTE Last minute changes and notes about the release. README.files This file. patches/ Post-release binary code patches. shared/ Binary sets shared between multiple ports. source/ Source code. source/sets/ Source distribution sets; see below. source/patches/ Post-release source code patches. In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD XXX.XXX has a binary distribution. The contents of each architecture's directory are described in an "INSTALL" file found in that directory. The most recent list of mirror sites for NetBSD is viewable at the URL: http://www.NetBSD.org/Sites/net.html If you are receiving this distribution on a CD set, some files and subdirectories may be on a separate disc; read all README files for more information. See http://www.NetBSD.org/Misc/crypto-export.html for the formal status of the exportability out of the United States of some pieces of the distribution tree containing cryptographic software. If you export these bits and the above document says you should not do so, it's your fault, not ours.