From des at linpro.no  Thu Feb 14 09:53:43 2008
From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=)
Date: Thu, 14 Feb 2008 10:53:43 +0100
Subject: varnishlog
Message-ID: <ujr8x1n6ezc.fsf@login.linpro.no>

I believe that both the Debian and RedHat packages enable varnishlog
by default, is that correct?

The problem is that varnishlog generates enormous amounts of data, and
consumes a fair bit of CPU doing so.  Therefore, I think varnishlog
should be disabled by default.

DES
-- 
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no


From ingvar at linpro.no  Thu Feb 14 10:49:11 2008
From: ingvar at linpro.no (Ingvar Hagelund)
Date: Thu, 14 Feb 2008 11:49:11 +0100
Subject: varnishlog
In-Reply-To: <ujr8x1n6ezc.fsf@login.linpro.no>
References: <ujr8x1n6ezc.fsf@login.linpro.no>
Message-ID: <47B41CA7.3000208@linpro.no>

* Dag-Erling Sm?rgrav
> I believe that both the Debian and RedHat packages enable varnishlog
> by default, is that correct?
> 
> The problem is that varnishlog generates enormous amounts of data, and
> consumes a fair bit of CPU doing so.  Therefore, I think varnishlog
> should be disabled by default.

In the RedHat package, a startup script is installed and added to the 
chkconfig system, but it is not started after installation, and it is 
not set up to start automatically at boot time. The user has to do this 
manually, like 'service varnishlog start' and 'chkconfig varnishlog on'.

The post update script restarts varnishlog (and varnishd) if it is running.

Ingvar

-- 
Buddha wears an iPod


From des at linpro.no  Thu Feb 14 11:12:50 2008
From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=)
Date: Thu, 14 Feb 2008 12:12:50 +0100
Subject: varnishlog
In-Reply-To: <47B41CA7.3000208@linpro.no> (Ingvar Hagelund's message of "Thu, 
	14 Feb 2008 11:49:11 +0100")
References: <ujr8x1n6ezc.fsf@login.linpro.no> <47B41CA7.3000208@linpro.no>
Message-ID: <ujr4pcbssel.fsf@login.linpro.no>

Ingvar Hagelund <ingvar at linpro.no> writes:
> In the RedHat package, a startup script is installed and added to the
> chkconfig system, but it is not started after installation, and it is
> not set up to start automatically at boot time. The user has to do
> this manually, like 'service varnishlog start' and 'chkconfig
> varnishlog on'.

Excellent, no change required for RedHat then.

DES
-- 
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no


From ssm at linpro.no  Mon Feb 18 05:51:14 2008
From: ssm at linpro.no (Stig Sandbeck Mathisen)
Date: Mon, 18 Feb 2008 06:51:14 +0100
Subject: varnishlog
In-Reply-To: <ujr8x1n6ezc.fsf@login.linpro.no> (Dag-Erling =?utf-8?Q?Sm?=
	=?utf-8?Q?=C3=B8rgrav's?= message
	of "Thu, 14 Feb 2008 10:53:43 +0100")
References: <ujr8x1n6ezc.fsf@login.linpro.no>
Message-ID: <7xy79i7qy5.fsf@iostat.linpro.no>

Dag-Erling Sm?rgrav <des at linpro.no> writes:

> I believe that both the Debian and RedHat packages enable varnishlog
> by default, is that correct?

For Debian, at least, yes.

> The problem is that varnishlog generates enormous amounts of data,
> and consumes a fair bit of CPU doing so.  Therefore, I think
> varnishlog should be disabled by default.

I guess...

Problem is, most of my Varnish installations are previous squid sites,
and varnish + varnishlog is less resource intensive than squid, while
performing better.  Having a detailed log available by default is
incredibly useful, particularly for new sites.

Or maybe I'm more fond of having data for debugging than available
diskspace.

-- 
Stig Sandbeck Mathisen, Linpro


From fredrik.nygren at gotamedia.se  Fri Feb 29 13:18:08 2008
From: fredrik.nygren at gotamedia.se (Fredrik Nygren)
Date: Fri, 29 Feb 2008 14:18:08 +0100
Subject: Request for RH EL4 RPM 1.1.2
Message-ID: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se>

Hi,
Varnish 1.1.2-5 seems to deliver blank pages when the request is done  
with HTTP/1.0. This problem should be fixed in the current trunk  
according to this ticket:
http://varnish.projects.linpro.no/ticket/197

I would appreciate if somebody wants to share rpm's for Redhat EL4  
i386 with this patch included.

Regards
<fredrik />