svn commit: r232945 - in stable/9: share/man/man4 sys/i386/conf sys/netinet sys/sys

Maxim Sobolev sobomax at FreeBSD.org
Mon Nov 11 00:09:08 UTC 2013


Thanks, Gleb, we'll give it a go!

-Maxim
On Nov 7, 2013 11:42 PM, "Gleb Smirnoff" <glebius at freebsd.org> wrote:

> On Thu, Nov 07, 2013 at 03:10:27PM -0800, Maxim Sobolev wrote:
> M> Hey guys, any particular reasons why those options are write-only? Is it
> M> just laziness of the developer or is there any particular fundamental
> M> reason for it being like this. This might be some regression, since at
> M> least some 3rd party software that does getsockopt(), checks its status
> and
> M> only does setsockopt() if the former completed successfully. Which kinda
> M> makes sense IMHO. The software in question is PostgreSQL here. As a
> result,
> M> the software may be misbehaving since it detects those options as being
> M> present on the configure stage, but cannot really make any use of them
> M> later on during runtime. Had it not detect those options at the build
> M> stage, it might have used some kind of software protocol workaround
> (i.e.
> M> sending ping/nop packets) so it in fact might trigger some bugs and
> whatnot.
> M>
> M> We believe it might be the reason for some of our problems here with PG
> 91
> M> and FreeBSD 92.
>
> Can you please try attached patch and report?
>
>
> --
> Totus tuus, Glebius.
>


More information about the freebsd-stable mailing list