MIME-Version: 1.0 In-Reply-To: X-Mailer: MIME-tools 5.505 (Entity 5.505) Content-Disposition: inline X-RT-Interface: Web References: Content-Type: text/plain; charset="utf-8" Message-ID: Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 RT-Send-CC: X-RT-Encrypt: 0 X-RT-Sign: 0 Content-Length: 997 On Fri Feb 24 14:43:26 2017, mat@FreeBSD.org wrote: > It seems users are quite keen on not having anything in their logs, as > the people in the threads quoted in this PR > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217288 are saying. > > > Maybe the "error" message could be less "hey, it's broken" and more > "everything is fine but this bit won't work". I don't know. => It seems to change the error/warning message or to add a configure option won't be enough (for the first users want no message, for the second they use packages). My only idea is to add a FreeBSD specific code which checks if the TCP_FASTOPEN feature was enabled: - the service socket is opened at start up so there is no need to handle system configuration changes - sysctl should provide the required information - I have used FreeBSD since more than 20 years (I can remember 2.x versions) - unfortunately the new release will be published soon so this will be at least for the next one... Thanks