This sounds an awful lot like "no PAE kernel" -- i.e., 32 bits and a really
old OS.
--Michael
On Fri, Jun 20, 2008 at 2:42 AM, kuku li <[EMAIL PROTECTED]> wrote:
> Hello,
>
> we have been running varnish for a while but noticed that varnish will just
> restart itself as the virtual memory goes t
Hello,
i am new to Varnish and i have some questions about the differents
versions. First i installed the 1.1.2 release with the .deb packages but
i browsed the mail list, and i saw many answers where people where were
advising to install a newer version from the svn.
In fact i would like to u
In message <[EMAIL PROTECTED]>, Wichert Akkerman writes:
>Previously Poul-Henning Kamp wrote:
>> Those of you running -trunk should take note of this commit if
>> you use regsub() in your VCL.
>>
>> I apologize for this kind of disruptive change, but the replacement
>> syntax was badly chosen and
Previously Poul-Henning Kamp wrote:
> Those of you running -trunk should take note of this commit if
> you use regsub() in your VCL.
>
> I apologize for this kind of disruptive change, but the replacement
> syntax was badly chosen and I needed to fix it before 2.0
This and the changes from
http:/
Those of you running -trunk should take note of this commit if
you use regsub() in your VCL.
I apologize for this kind of disruptive change, but the replacement
syntax was badly chosen and I needed to fix it before 2.0
Poul-Henning
--
In message <[EMAIL PROTECTED]>, "kuku
li" writes:
>we have been running varnish for a while but noticed that varnish will just
>restart itself as the virtual memory goes to 3G(from the linux top command)
>and the cache hit rate consequently drop to almost 0%. Is it a known bug or
>we just missed
Hello,
we have been running varnish for a while but noticed that varnish will just
restart itself as the virtual memory goes to 3G(from the linux top command)
and the cache hit rate consequently drop to almost 0%. Is it a known bug or
we just missed something important?
Thanks.
_
In message <[EMAIL PROTECTED]>, "anda
n andan" writes:
>Hello.
>
>It is possible to disable sysloging for the CLI sessions, or at least,
>change the priority or facility. ?
Not without hacking the code, search for "syslog" in mgt_cli.c.
>We are using Varnish (trunk) with LVS, pinging varnish to
