The package varnish has been upgraded to 4.1.0-1, leaving 3.0.5-1 as
previous.
PACKAGE DESCRIPTION
===
Varnish is a web accelerator written with performance and flexibility in
mind.
Varnish store web pages in memory so the web servers don't have to create
the same web page over
escribió:
On Jul 24 14:22, jdzstz wrote:
Hello,
I am preparing the new version 4.0.1 of Varnish.
I am using a Windows 8.1 machine, with all hotfix installed.
I have updated cygwin to 1.7.31-2 and launch Varnish package tests and some
failed at "write" function.
After some investigations d
Hello,
I am preparing the new version 4.0.1 of Varnish.
I am using a Windows 8.1 machine, with all hotfix installed.
I have updated cygwin to 1.7.31-2 and launch Varnish package tests and
some failed at "write" function.
After some investigations downloading snapshots, I have verified that:
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
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
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 getsockopt:
The package varnish has been upgraded to 3.0.5-1, leaving 3.0.2-1 as
previous.
This is the first 64 bits package release of varnish
PACKAGE DESCRIPTION
===
Varnish is a web accelerator written with performance and flexibility in
mind.
Varnish store web pages in memory so the web
The package varnish has been upgraded to 3.0.2-1, leaving 2.1.5-1 as
previous.
PACKAGE DESCRIPTION
===
Varnish is a web accelerator written with performance and flexibility in mind.
Varnish store web pages in memory so the web servers don't have to create
the same web page over and
The package varnish has been upgraded to 3.0.2-1, leaving 2.1.5-1 as
previous.
PACKAGE DESCRIPTION
===
Varnish is a web accelerator written with performance and flexibility in mind.
Varnish store web pages in memory so the web servers don't have to create
the same web page over and
Hello,
Last current cygwin version 1.7.9 was released 6 months ago, there is
any planned date to release future 1.7.10 version ?
( I am going to create new version 3.0 of varnish cache cygwin
package, and I prefer to wait to cygwin 1.7.10 in case of the release
date is upcoming. )
Thanks,
--
P
Version 2.1.5-1 of "varnish" has been uploaded.
Varnish is a web accelerator written with performance and flexibility in mind.
It's modern architecture gives it a significantly better performance than many
of it's competing products.
Changelog
=
- Updated to varnish 2.1.5 version
Version 2.1.5-1 of "varnish" has been uploaded.
Varnish is a web accelerator written with performance and flexibility in mind.
It's modern architecture gives it a significantly better performance than many
of it's competing products.
Changelog
=
- Updated to varnish 2.1.5 version
About ncurses library, you can get rid of all terminfo files if you
replace ncurses with pdcurses: http://pdcurses.sourceforge.net/
I have compiled varnish cache with pdcurses and it works fine.
You have to:
* compile pdcurses library in cygwin
* include curses.h files of pdcurses instead n
I have tested the bugs I reported about Varnish Cache program and It
works fine with last snapshot:
- Make sure that the random number generator is seeded on a
per-thread basis.
- Fix bind(2) behaviour related to SO_REUSEADDR.
and they works ok. New madvise call also works ok.
--
Problem
>
> The Cygwin workaround to fix the WinSock SO_REUSEADDR behaviour from
> back in 2006 was not so nifty after all. I just fixed that in CVS. I'm
> going to generate a new developer snapshot right now. Should be up in a
> couple of minutes.
>
Using cygwin snapshot, the testcase and varnishtest
I have detected an issue in windows xp with socket SO_REUSEADDR when a
tcp client keeps connected forever.
I don't know if it is a cygwin bug or a problem with microsoft winsock
implementation. I don't know if windows vista or windows 7 has the
same behaviour.
I have a server process that open a
>
> Thanks for the testcase! I applied a patch to Cygwin which should fix
> this for all socket functions which potentially block.
>
> Please test the latest developer snapshot (create today) from
> http://cygwin.com/snapshots/
>
I have executed my testcase with last cygwin snapshot and works ok.
I have detected an issue with pthread_join when the thread is
executing "accept" TCP function.
If a thread is blocked in an accept TCP call, and a "pthread_cancel"
and "pthread_join" are called from parent, in cygwin, the
"pthread_join" is blocked forever until "accept" ends (that maybe
never end)
I have detected a strange issue with IPv6 and mmap in Windows XP.
I want to execute varnish program from windows cmd.exe, launching a BAT file.
If IPv6 is deactivated (default in windows xp) all works OK.
But if I activate IPV6 with following comand:
C:\WINDOWS>netsh
netsh>interface
netsh interf
Version 2.1.4-5 of "varnish" has been uploaded.
Varnish cache software has been released successfully in Cygwin environment.
Varnish is a web accelerator written with performance and flexibility in mind.
It's modern architecture gives it a significantly better performance than many
of it's compet
I have readed again the Linux man page
http://www.kernel.org/doc/man-pages/online/pages/man2/madvise.2.html
and perhaps the first text is outdated.
At the beginning of man page it says that:
"This call does not influence the semantics of the application (except
in the case of MADV_DONTNEED), but m
f posix_madvise constants:
#define MADV_NORMAL POSIX_MADV_NORMAL
#define MADV_SEQUENTIAL POSIX_MADV_SEQUENTIAL
#define MADV_RANDOM POSIX_MADV_RANDOM
#define MADV_WILLNEED POSIX_MADV_WILLNEED
#define MADV_DONTNEED POSIX_MADV_DONTNEED
2011/1/11 Eric Blake:
> On 01/11/2011 04:13 AM
Testing a linux application that uses "madvise", varnish cache, I have
realized that in cygwin doesnot exists this function but exists the
alternative "posix_madvise".
Adding inside configure.ac script:
+ AC_DEFINE([madvise], [posix_madvise], [In CYGWIN, madvise
function
is not defi
About all the problems with drand48, explained in:
* http://www.cygwin.com/ml/cygwin/2010-12/msg00460.html
Christopher Faylor fixed it in 20101229 snapshot:
http://www.cygwin.com/snapshots/winsup-changelog-20101226-20101229
I have realized that the fix does not work as expected, it is used
thr
24 matches
Mail list logo
