From des at linpro.no Mon Mar 3 10:19:45 2008 From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Mon, 03 Mar 2008 11:19:45 +0100 Subject: varnishlog In-Reply-To: <7xy79i7qy5.fsf@iostat.linpro.no> (Stig Sandbeck Mathisen's message of "Mon, 18 Feb 2008 06:51:14 +0100") References: <7xy79i7qy5.fsf@iostat.linpro.no> Message-ID: Stig Sandbeck Mathisen writes: > 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. I think varnishncsa delivers the kind of logs people are used to from Squid. Enabling varnishncsa by default is fine, but varnishlog will fill up people's disks too quickly, and they may not even be aware of it before their log partition is full. > Or maybe I'm more fond of having data for debugging than available > diskspace. The problem is that we're talking *lots* of disk space... perhaps around 1 kB per request. DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From des at linpro.no Mon Mar 3 10:50:53 2008 From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Mon, 03 Mar 2008 11:50:53 +0100 Subject: Request for RH EL4 RPM 1.1.2 In-Reply-To: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se> (Fredrik Nygren's message of "Fri, 29 Feb 2008 14:18:08 +0100") References: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se> Message-ID: Fredrik Nygren writes: > 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 The patch in the PR is based on an incorrect understanding of the code. The bug was fixed in r2091 in trunk, and can be obtained with 'svn diff -c2091' in a trunk checkout. I will merge it to 1.1 ASAP. DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From fredrik.nygren at gotamedia.se Mon Mar 3 14:12:54 2008 From: fredrik.nygren at gotamedia.se (Fredrik Nygren) Date: Mon, 3 Mar 2008 15:12:54 +0100 Subject: Request for RH EL4 RPM 1.1.2 In-Reply-To: References: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se> Message-ID: I tried to build my own rpm's for RH EL4 from instructions you sent to Ramon A Hermon. But unfortunately my environment seems to missing rpmbuild and automake (and possibly other needed tools). Therefore I kindly ask the list for help with building rpm's for Redhat EL4. Regards On 3 mar 2008, at 11.50, Dag-Erling Sm?rgrav wrote: Fredrik Nygren writes: > 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 The patch in the PR is based on an incorrect understanding of the code. The bug was fixed in r2091 in trunk, and can be obtained with 'svn diff -c2091' in a trunk checkout. I will merge it to 1.1 ASAP. DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From des at linpro.no Mon Mar 3 14:49:46 2008 From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Mon, 03 Mar 2008 15:49:46 +0100 Subject: Request for RH EL4 RPM 1.1.2 In-Reply-To: (Fredrik Nygren's message of "Mon, 3 Mar 2008 15:12:54 +0100") References: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se>

Message-ID: Fredrik Nygren writes: > I tried to build my own rpm's for RH EL4 from instructions you sent to > Ramon A Hermon. But unfortunately my environment seems to missing > rpmbuild and automake (and possibly other needed tools). Therefore I > kindly ask the list for help with building rpm's for Redhat EL4. You should only need rpmbuild, autoconf, automake and libtool. They should all be part of the standard assortment of packages that come with your OS (i.e. they should be on the installation CD or DVD that you used). DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From fredrik.nygren at gotamedia.se Mon Mar 3 16:02:51 2008 From: fredrik.nygren at gotamedia.se (Fredrik Nygren) Date: Mon, 3 Mar 2008 17:02:51 +0100 Subject: Request for RH EL4 RPM 1.1.2 In-Reply-To: References: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se>

Message-ID: <465A2D55-15F5-4858-9AD1-219D5C88782C@gotamedia.se> Alright... I will give it another try. But do I have to change anything else? varnish.spec for example? Regards On 3 mar 2008, at 15.49, Dag-Erling Sm?rgrav wrote: Fredrik Nygren writes: > I tried to build my own rpm's for RH EL4 from instructions you sent to > Ramon A Hermon. But unfortunately my environment seems to missing > rpmbuild and automake (and possibly other needed tools). Therefore I > kindly ask the list for help with building rpm's for Redhat EL4. You should only need rpmbuild, autoconf, automake and libtool. They should all be part of the standard assortment of packages that come with your OS (i.e. they should be on the installation CD or DVD that you used). DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From des at linpro.no Mon Mar 3 16:31:30 2008 From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Mon, 03 Mar 2008 17:31:30 +0100 Subject: Request for RH EL4 RPM 1.1.2 In-Reply-To: <465A2D55-15F5-4858-9AD1-219D5C88782C@gotamedia.se> (Fredrik Nygren's message of "Mon, 3 Mar 2008 17:02:51 +0100") References: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se>

<465A2D55-15F5-4858-9AD1-219D5C88782C@gotamedia.se> Message-ID: Fredrik Nygren writes: > Alright... I will give it another try. But do I have to change > anything else? varnish.spec for example? Yes, you need to find the line in redhat/varnish.spec that says # ./autogen.sh and change it to ./autogen.sh DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From fredrik.nygren at gotamedia.se Tue Mar 4 08:41:41 2008 From: fredrik.nygren at gotamedia.se (Fredrik Nygren) Date: Tue, 4 Mar 2008 09:41:41 +0100 Subject: Request for RH EL4 RPM 1.1.2 In-Reply-To: References: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se>

<465A2D55-15F5-4858-9AD1-219D5C88782C@gotamedia.se> Message-ID: <657AA9C9-63BA-493A-A47A-1EA39D715FB2@gotamedia.se> Easy even for me ;-) Apart from automake, autoconf and libtool the build process also wanted ncurses-devel. I changed the varnish.spec and then tried the rpmbuild command. Unfortunately something went wrong. Here's the output: [root at sehan9078gota1 varnish]# rpmbuild -tb varnish-1.1.2.tar.gz Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.99170 + umask 022 + cd /usr/src/redhat/BUILD + cd /usr/src/redhat/BUILD + rm -rf varnish-1.1.2 + /bin/gzip -dc /home/xlibris/varnish/varnish-1.1.2.tar.gz + tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd varnish-1.1.2 ++ /usr/bin/id -u + '[' 0 = 0 ']' + /bin/chown -Rhf root . ++ /usr/bin/id -u + '[' 0 = 0 ']' + /bin/chgrp -Rhf root . + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + ./autogen.sh + aclocal + libtoolize --copy --force + autoheader + automake --add-missing --copy --foreign configure.ac: installing `./install-sh' configure.ac: installing `./missing' bin/varnishadm/Makefile.am: installing `./compile' bin/varnishadm/Makefile.am: installing `./depcomp' + autoconf + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.47906 + umask 022 + cd /usr/src/redhat/BUILD + cd varnish-1.1.2 + CFLAGS='-O2 -g -march=i386 -mcpu=i686' + export CFLAGS + CXXFLAGS='-O2 -g -march=i386 -mcpu=i686' + export CXXFLAGS + FFLAGS='-O2 -g -march=i386 -mcpu=i686' + export FFLAGS + ./configure --host=i686-redhat-linux-gnu --build=i686-redhat-linux- gnu --target=i386-redhat-linux --program-prefix= --prefix=/usr --exec- prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc -- datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib -- libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --disable-static -- localstatedir=/var/lib checking build system type... i686-redhat-linux-gnu checking host system type... i686-redhat-linux-gnu checking target system type... i386-redhat-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-redhat-linux-gnu-gcc... no checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking for a sed that does not truncate output... /bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... nm checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for i686-redhat-linux-gnu-g++... no checking for i686-redhat-linux-gnu-c++... no checking for i686-redhat-linux-gnu-gpp... no checking for i686-redhat-linux-gnu-aCC... no checking for i686-redhat-linux-gnu-CC... no checking for i686-redhat-linux-gnu-cxx... no checking for i686-redhat-linux-gnu-cc++... no checking for i686-redhat-linux-gnu-cl... no checking for i686-redhat-linux-gnu-FCC... no checking for i686-redhat-linux-gnu-KCC... no checking for i686-redhat-linux-gnu-RCC... no checking for i686-redhat-linux-gnu-xlC_r... no checking for i686-redhat-linux-gnu-xlC... no checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking dependency style of g++... none checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. error: Bad exit status from /var/tmp/rpm-tmp.47906 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.47906 (%build) I checked the config.log file and last log messages is: ## ----------- ## ## confdefs.h. ## ## ----------- ## #define HAVE_DLFCN_H 1 #define HAVE_INTTYPES_H 1 #define HAVE_MEMORY_H 1 #define HAVE_STDINT_H 1 #define HAVE_STDLIB_H 1 #define HAVE_STRINGS_H 1 #define HAVE_STRING_H 1 #define HAVE_SYS_STAT_H 1 #define HAVE_SYS_TYPES_H 1 #define HAVE_UNISTD_H 1 #define PACKAGE "varnish" #define PACKAGE_BUGREPORT "varnish-dev at projects.linpro.no" #define PACKAGE_NAME "Varnish" #define PACKAGE_STRING "Varnish 1.1.2" #define PACKAGE_TARNAME "varnish" #define PACKAGE_VERSION "1.1.2" #define STDC_HEADERS 1 #define VERSION "1.1.2" #define _GNU_SOURCE 1 #endif #ifdef __cplusplus void exit (int); configure: exit 1 On my Feodora box rpmbuild creates the rpm's successfully, but not on my Redhat EL 4. Advice is appreciated. Regards On 3 mar 2008, at 17.31, Dag-Erling Sm?rgrav wrote: Fredrik Nygren writes: > Alright... I will give it another try. But do I have to change > anything else? varnish.spec for example? Yes, you need to find the line in redhat/varnish.spec that says # ./autogen.sh and change it to ./autogen.sh DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From des at linpro.no Tue Mar 4 09:50:19 2008 From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Tue, 04 Mar 2008 10:50:19 +0100 Subject: Request for RH EL4 RPM 1.1.2 In-Reply-To: <657AA9C9-63BA-493A-A47A-1EA39D715FB2@gotamedia.se> (Fredrik Nygren's message of "Tue, 4 Mar 2008 09:41:41 +0100") References: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se>

<465A2D55-15F5-4858-9AD1-219D5C88782C@gotamedia.se> <657AA9C9-63BA-493A-A47A-1EA39D715FB2@gotamedia.se> Message-ID: Fredrik Nygren writes: > Easy even for me ;-) Apart from automake, autoconf and libtool the > build process also wanted ncurses-devel. Ah, right. We removed that in trunk (it will just skip the ncurses parts if you don't have it), but not in 1.1. > checking how to run the C++ preprocessor... /lib/cpp > configure: error: C++ preprocessor "/lib/cpp" fails sanity check > See `config.log' for more details. > error: Bad exit status from /var/tmp/rpm-tmp.47906 (%build) > > RPM build errors: > Bad exit status from /var/tmp/rpm-tmp.47906 (%build) > > I checked the config.log file and last log messages is: The last log message is irrelevant, it's always the same. What's interesting is the error message that comes a few dozen lines further up. It would be easiest if you would just mail me the entire file. DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From fredrik.nygren at gotamedia.se Tue Mar 4 10:01:24 2008 From: fredrik.nygren at gotamedia.se (Fredrik Nygren) Date: Tue, 4 Mar 2008 11:01:24 +0100 Subject: Request for RH EL4 RPM 1.1.2 In-Reply-To: References: <98DE1514-63C9-4D3A-81CC-8C505C5CCB74@gotamedia.se>

<465A2D55-15F5-4858-9AD1-219D5C88782C@gotamedia.se> <657AA9C9-63BA-493A-A47A-1EA39D715FB2@gotamedia.se> Message-ID: The problem is solved. The missing piece was gcc-c++. When we installed that package the build process executed without problems. Thank you for your help. Regards On 4 mar 2008, at 10.50, Dag-Erling Sm?rgrav wrote: Fredrik Nygren writes: > Easy even for me ;-) Apart from automake, autoconf and libtool the > build process also wanted ncurses-devel. Ah, right. We removed that in trunk (it will just skip the ncurses parts if you don't have it), but not in 1.1. > checking how to run the C++ preprocessor... /lib/cpp > configure: error: C++ preprocessor "/lib/cpp" fails sanity check > See `config.log' for more details. > error: Bad exit status from /var/tmp/rpm-tmp.47906 (%build) > > RPM build errors: > Bad exit status from /var/tmp/rpm-tmp.47906 (%build) > > I checked the config.log file and last log messages is: The last log message is irrelevant, it's always the same. What's interesting is the error message that comes a few dozen lines further up. It would be easiest if you would just mail me the entire file. DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From fredrik.nygren at gotamedia.se Tue Mar 4 12:22:02 2008 From: fredrik.nygren at gotamedia.se (Fredrik Nygren) Date: Tue, 4 Mar 2008 13:22:02 +0100 Subject: Varnish 1.1.2-6 RPM for Redhat EL 4 Message-ID: <78CBC7B1-C88E-4C20-8106-B58227DEA88D@gotamedia.se> Hi, If you're in need of newer rpm's, like I was, for Redhat EL 4 i386... Here you go. I called them 1.1.2-6 and the rpm files are attached. Regards -------------- next part -------------- A non-text attachment was scrubbed... Name: varnish-1.1.2-6.i386.rpm Type: application/x-rpm Size: 170187 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: varnish-libs-1.1.2-6.i386.rpm Type: application/x-rpm Size: 109700 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: varnish-libs-devel-1.1.2-6.i386.rpm Type: application/x-rpm Size: 10612 bytes Desc: not available URL: -------------- next part -------------- From ingvar at linpro.no Tue Mar 4 14:11:46 2008 From: ingvar at linpro.no (Ingvar Hagelund) Date: Tue, 04 Mar 2008 15:11:46 +0100 Subject: Varnish 1.1.2-6 RPM for Redhat EL 4 In-Reply-To: <78CBC7B1-C88E-4C20-8106-B58227DEA88D@gotamedia.se> References: <78CBC7B1-C88E-4C20-8106-B58227DEA88D@gotamedia.se> Message-ID: <47CD58A2.9060805@linpro.no> * Fredrik Nygren > If you're in need of newer rpm's, like I was, for Redhat EL 4 i386... > Here you go. > > I called them 1.1.2-6 and the rpm files are attached. To not break upgrades, please use a version naming convention that won't break Red Hat's upgrade algorithm. A build of a pre-1.1.3 svn checkout should be named something like varnish-1.1.3-0.1.20080304svn ... or in specfile format: Version: 1.1.3 Release: 0.1.20080304svn This makes it possible to upgrade to a newer svn checkout, or an upstream release varnish-1.1.3-1. A patched build of 1.1.2 should be named something like varnish-1.1.2-5.1.mypatchfixesfoo ... or in specfile format: Version: 1.1.2 Release: 5.1.mypatchfixesfoo In this way, it's possible to upgrade from your built version to a new released version of 1.1.3 It's also visible that your patched version is based on a newer build than a current 1.1.2-5 and makes an upgrade to a newer upstream 1.1.2-6 from the varnish team possible. You may even add another patch, and call varnish-1.1.2-5.2.evenmorepatchedversionfoo and so on to ensure easy package upgrading. btw, I didn't think you needed the preprocessor for gcc-c++ to make varnish build. Is this really so? Ingvar -- Buddha wears an iPod From fredrik.nygren at gotamedia.se Wed Mar 5 13:47:42 2008 From: fredrik.nygren at gotamedia.se (Fredrik Nygren) Date: Wed, 5 Mar 2008 14:47:42 +0100 Subject: Varnish 1.1.2-6 RPM for Redhat EL 4 In-Reply-To: <47CD58A2.9060805@linpro.no> References: <78CBC7B1-C88E-4C20-8106-B58227DEA88D@gotamedia.se> <47CD58A2.9060805@linpro.no> Message-ID: I'm sorry. This was the first time I built rpm packages . I'm newbie as you already know. I just followed the instructions here: http://projects.linpro.no/pipermail/varnish-misc/2008-March/001438.html The bug caused us a lot of problem and we couldn't wait for the official packages. I hope we can do some kind of rollback when the official packages will arrive. But it solved our urgent problems. Unfortunately not in a handsome way. I'm grateful you told me the right way to do it. The rpm build process failed without the gcc-c++ package (which contains of libgcc, libstdc++, libstdc++-devel, cpp, gcc and gcc-c++) installed. I'm not sure if the whole gss-c++ was necessary or if it had been enough with just some of the included packages. Regards On 4 mar 2008, at 15.11, Ingvar Hagelund wrote: * Fredrik Nygren > If you're in need of newer rpm's, like I was, for Redhat EL 4 > i386... Here you go. > > I called them 1.1.2-6 and the rpm files are attached. To not break upgrades, please use a version naming convention that won't break Red Hat's upgrade algorithm. A build of a pre-1.1.3 svn checkout should be named something like varnish-1.1.3-0.1.20080304svn ... or in specfile format: Version: 1.1.3 Release: 0.1.20080304svn This makes it possible to upgrade to a newer svn checkout, or an upstream release varnish-1.1.3-1. A patched build of 1.1.2 should be named something like varnish-1.1.2-5.1.mypatchfixesfoo ... or in specfile format: Version: 1.1.2 Release: 5.1.mypatchfixesfoo In this way, it's possible to upgrade from your built version to a new released version of 1.1.3 It's also visible that your patched version is based on a newer build than a current 1.1.2-5 and makes an upgrade to a newer upstream 1.1.2-6 from the varnish team possible. You may even add another patch, and call varnish-1.1.2-5.2.evenmorepatchedversionfoo and so on to ensure easy package upgrading. btw, I didn't think you needed the preprocessor for gcc-c++ to make varnish build. Is this really so? Ingvar -- Buddha wears an iPod From des at linpro.no Wed Mar 5 14:56:52 2008 From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Wed, 05 Mar 2008 15:56:52 +0100 Subject: Varnish 1.1.2-6 RPM for Redhat EL 4 In-Reply-To: (Fredrik Nygren's message of "Wed\, 5 Mar 2008 14\:47\:42 +0100") References: <78CBC7B1-C88E-4C20-8106-B58227DEA88D@gotamedia.se> <47CD58A2.9060805@linpro.no> Message-ID: <8763w1z0az.fsf@des.linpro.no> Fredrik Nygren writes: > The rpm build process failed without the gcc-c++ package (which > contains of libgcc, libstdc++, libstdc++-devel, cpp, gcc and gcc-c++) > installed. I'm not sure if the whole gss-c++ was necessary or if it > had been enough with just some of the included packages. gcc and cpp + their dependencies should suffice. DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From des at linpro.no Fri Mar 7 14:13:31 2008 From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Fri, 07 Mar 2008 15:13:31 +0100 Subject: RLIMIT_MEMLOCK Message-ID: <871w6mei5w.fsf@des.linpro.no> Starting with r2561, Varnish will attempt to lock the shared memory log in memory. On some systems, this will fail due to RLIMIT_MEMLOCK being too low. It may be a good idea to have the default init script set it to a reasonably large value. The default log size is 80 MB + header, so something like 'ulimit -l 82000' should be fine. DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From ingvar at linpro.no Fri Mar 7 15:11:10 2008 From: ingvar at linpro.no (Ingvar Hagelund) Date: Fri, 07 Mar 2008 16:11:10 +0100 Subject: RLIMIT_MEMLOCK In-Reply-To: <871w6mei5w.fsf@des.linpro.no> References: <871w6mei5w.fsf@des.linpro.no> Message-ID: <47D15B0E.1060202@linpro.no> * Dag-Erling Sm?rgrav > Starting with r2561, Varnish will attempt to lock the shared memory log > in memory. On some systems, this will fail due to RLIMIT_MEMLOCK being > too low. It may be a good idea to have the default init script set it > to a reasonably large value. The default log size is 80 MB + header, so > something like 'ulimit -l 82000' should be fine. Fixed in trunk for redhat. Ingvar -- Buddha wears an iPod From ssm at linpro.no Mon Mar 10 06:02:29 2008 From: ssm at linpro.no (Stig Sandbeck Mathisen) Date: Mon, 10 Mar 2008 07:02:29 +0100 Subject: RLIMIT_MEMLOCK In-Reply-To: <871w6mei5w.fsf@des.linpro.no> (Dag-Erling =?utf-8?Q?Sm=C3=B8?= =?utf-8?Q?rgrav's?= message of "Fri, 07 Mar 2008 15:13:31 +0100") References: <871w6mei5w.fsf@des.linpro.no> Message-ID: <7xtzjf2k22.fsf@iostat.linpro.no> Dag-Erling Sm?rgrav writes: > It may be a good idea to have the default init script set it to a > reasonably large value. The default log size is 80 MB + header, so > something like 'ulimit -l 82000' should be fine. Fixed in trunk for Debian. -- Stig Sandbeck Mathisen, Linpro