From owner-cvs-all@FreeBSD.ORG Wed Dec 31 21:41:08 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D348016A4CE; Wed, 31 Dec 2003 21:41:08 -0800 (PST) Received: from horsey.gshapiro.net (horsey.gshapiro.net [64.105.95.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAC5D43D54; Wed, 31 Dec 2003 21:41:06 -0800 (PST) (envelope-from gshapiro@gshapiro.net) Received: from horsey.gshapiro.net (localhost [127.0.0.1]) id i015f6xh009435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Dec 2003 21:41:06 -0800 (PST) Received: (from gshapiro@localhost)i015f6nk009434; Wed, 31 Dec 2003 21:41:06 -0800 (PST) Date: Wed, 31 Dec 2003 21:41:06 -0800 From: Gregory Neil Shapiro To: Doug Barton Message-ID: <20040101054105.GY10635@horsey.gshapiro.net> References: <200312311742.hBVHgGb2051373@repoman.freebsd.org> <20031231152909.U1441@bo.vpnaa.bet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031231152909.U1441@bo.vpnaa.bet> User-Agent: Mutt/1.5.5.1i cc: "cvs-src@FreeBSD.org" cc: "src-committers@FreeBSD.org" cc: freebsd-stable@freebsd.org cc: "cvs-all@FreeBSD.org" Subject: Re: cvs commit: src/etc/sendmail freebsd.mc X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jan 2004 05:41:09 -0000 > > Modified files: (Branch: RELENG_4) > > etc/sendmail freebsd.mc > > Log: > > MFC: Enable IPv6 by default but make it optional so it doesn't affect > > sites without IPv6. > What happens if I have a RELENG_4 system, with no IPv6 enabled, and I > mergemaster this change into my system? If everything keeps working with > no errors, then I think enabling this by default is probably ok. If not, > then I'd be concerned that this violotes the charter for -stable. As noted in the log, it won't affect sites (or machines) without IPv6 enabled. Actually, that isn't completely true. A machine with a non-IPv6 enabled kernel which uses the new configuration will get a syslog informational report when they start the daemon saying the optional socket was disabled but the MTA will continue to operate normally: Dec 31 21:06:23 scooter sm-mta[2184]: starting daemon (8.12.10): SMTP+queueing@00:30:00 Dec 31 21:06:23 scooter sm-mta[2184]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon IPv6: can't create server SMTP socket: Protocol not supported Dec 31 21:06:23 scooter sm-mta[2184]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon IPv6: optional socket disabled