Re: kgio, autopush test fails on Debian GNU/kFreeBSD

[Eric Wong <normalperson@yhbt.net>]

375gnu <375gnu@gmail.com> wrote:
> I know that it's an exotic system, but anyway.
> 
> In the last assertion getsockopt returns 0. May be it's good behavior for
> GNU/kFreeBSD, I don't know.

I think this problem is partially caused by eglibc/glibc failing to
define TCP_NOPUSH in the headers.   I can probably workaround it with
with something like:

#if defined(__GLIBC__) && defined(__FreeBSD_kernel__) && !defined(TCP_NOPUSH)
#  define TCP_NOPUSH 4
#endif

in ext/kgio/autopush.c   If it works, we should report this to the
Debian eglibc folks.

>   def test_autopush_accessors
>     Kgio.autopush = true
>     opt = RUBY_PLATFORM =~ /freebsd/ ? TCP_NOPUSH : TCP_CORK

And I suspect RUBY_PLATFORM is "gnu/kfreebsd" or something and
matches :x

I'll try to get this working on GNU/kFreeBSD this week if you don't beat
me to it.

It'd probably be a good idea to just add a Kgio.autopush_capable?
method to the API, to avoid problems like this in the future, too...