Hi,
Thank you about the information.
Regards,
Jorge Díaz
El 07/05/2014 9:51, Corinna Vinschen escribió:
On May 7 00:44, jdzstz wrote:
Hi Corinna,
I have recompiled and tested Varnish Cache 3.0.5 against cygwin
snapshot 2014-05-05 (64 bits), removing my workaround, and now
TCP_NODELAY functi
On May 7 00:44, jdzstz wrote:
> Hi Corinna,
>
> I have recompiled and tested Varnish Cache 3.0.5 against cygwin
> snapshot 2014-05-05 (64 bits), removing my workaround, and now
> TCP_NODELAY functionality works fine.
>
> In order to planning the release of fixed varnish 3.0.5, Do you have
> any
Hi Corinna,
I have recompiled and tested Varnish Cache 3.0.5 against cygwin snapshot
2014-05-05 (64 bits), removing my workaround, and now TCP_NODELAY
functionality works fine.
In order to planning the release of fixed varnish 3.0.5, Do you have any
estimated release date for future Cygwin
On May 5 14:34, Corinna Vinschen wrote:
> Only, starting with Windows Vista, getsockopt suddenly returned with
> optlen set to 1, which is sizeof(BOOLEAN), the boolean type used by the
> underlying kernel. And this has never been fixed again.
>
> Cygwin already handles this problem by converting
Hi Jorge,
On Apr 27 11:05, jdzstz wrote:
>
> While compiling varnish 3.0.5, I have detected a possible bug at
> getsockopt when TCP_NODELAY is used as parameter. The issue is
> caused because at cygwin it returns a BOOL, instead returning INT
> value like at Linux.
It's wors
While compiling varnish 3.0.5, I have detected a possible bug at
getsockopt when TCP_NODELAY is used as parameter. The issue is caused
because at cygwin it returns a BOOL, instead returning INT value like at
Linux.
At varnish 3.0.5, the following code at "sock_test(int fd)" uses
6 matches
Mail list logo
