September 2008 Archives by thread

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...

Starting: Mon Sep 1 15:07:30 UTC 2008
Ending: Tue Sep 30 13:42:12 UTC 2008
Messages: 205

• [Varnish] #304: Build fails on "undefined reference to `pthread_self'"   Varnish
  • [Varnish] #304: Build fails on "undefined reference to `pthread_self'"   Varnish
  • [Varnish] #304: Build fails on "undefined reference to `pthread_self'"   Varnish
  • [Varnish] #304: Build fails on "undefined reference to `pthread_self'"   Varnish
• [Varnish] #305: 2.0 beta1 cannot be built on MacOSX   Varnish
  • [Varnish] #305: 2.0 beta1 cannot be built on MacOSX   Varnish
• [Varnish] #306: Throwing 503 Service Unavailable despite healthy backend in director   Varnish
  • [Varnish] #306: Throwing 503 Service Unavailable despite healthy backend in director   Varnish
  • [Varnish] #306: Throwing 503 Service Unavailable despite healthy backend in director   Varnish
• [Varnish] #307: segfault in purge.hash() with empty string   Varnish
  • [Varnish] #307: segfault in purge.hash() with empty string   Varnish
  • [Varnish] #307: segfault in purge.hash() with empty string   Varnish
• [Varnish] #308: Worker threads reported 0   Varnish
  • [Varnish] #308: Worker threads reported 0   Varnish
  • [Varnish] #308: Worker threads reported 0   Varnish
  • [Varnish] #308: Worker threads reported 0   Varnish
• [Varnish] #297: make check fails on test a00007, fedora9, i386   Varnish
  • [Varnish] #297: make check fails on test a00007, fedora9, i386   Varnish
  • [Varnish] #297: make check fails on test a00007, fedora9, i386   Varnish
• [Varnish] #272: Assert error in vca_acct(), cache_acceptor.c line 173   Varnish
  • [Varnish] #272: Assert error in vca_acct(), cache_acceptor.c line 173   Varnish
  • [Varnish] #272: Assert error in vca_acct(), cache_acceptor.c line 173   Varnish
  • [Varnish] #272: Assert error in vca_acct(), cache_acceptor.c line 173   Varnish
• [Varnish] #309: Varnish freezes if >1k of binary postdata is passed in   Varnish
  • [Varnish] #309: Varnish freezes if >1k of binary postdata is passed in   Varnish
  • [Varnish] #309: Varnish freezes if >1k of binary postdata is passed in   Varnish
  • [Varnish] #309: Varnish freezes if >1k of binary postdata is passed in   Varnish
  • [Varnish] #309: Varnish freezes if >1k of binary postdata is passed in   Varnish
  • [Varnish] #309: Varnish freezes if >1k of binary postdata is passed in   Varnish
  • [Varnish] #309: Varnish freezes if >1k of binary postdata is passed in   Varnish
  • [Varnish] #309: Varnish freezes if >1k of binary postdata is passed in   Varnish
• [Varnish] #310: WS_Reserve panic + error   Varnish
  • [Varnish] #310: WS_Reserve panic + error   Varnish
  • [Varnish] #310: WS_Reserve panic + error   Varnish
  • [Varnish] #310: WS_Reserve panic + error   Varnish
  • [Varnish] #310: WS_Reserve panic + error   Varnish
  • [Varnish] #310: WS_Reserve panic + error   Varnish
  • [Varnish] #310: WS_Reserve panic + error   Varnish
  • [Varnish] #310: WS_Reserve panic + error   Varnish
  • [Varnish] #310: WS_Reserve panic + error   Varnish
• [Varnish] #311: varnishtest fails at c00005.vtc on ppc64   Varnish
  • [Varnish] #311: varnishtest fails at c00005.vtc on ppc64   Varnish
  • [Varnish] #311: varnishtest fails at c00005.vtc on ppc64   Varnish
  • [Varnish] #311: varnishtest fails at c00005.vtc on ppc64   Varnish
  • [Varnish] #311: varnishtest fails at c00005.vtc on ppc64   Varnish
  • [Varnish] #311: varnishtest fails at c00005.vtc on ppc64   Varnish
  • [Varnish] #311: varnishtest fails at c00005.vtc on ppc64   Varnish
  • [Varnish] #311: varnishtest fails at c00005.vtc on ppc64   Varnish
  • [Varnish] #311: varnishtest fails at c00005.vtc on ppc64   Varnish
• [Varnish] #312: No way to access backend health from VCL   Varnish
  • [Varnish] #312: No way to access backend health from VCL   Varnish
• [Varnish] #313: beta1 fails tests on Solaris   Varnish
  • [Varnish] #313: beta1 fails tests on Solaris   Varnish
• [Varnish] #314: undefined reference to `pthread_self'   Varnish
  • [Varnish] #314: undefined reference to `pthread_self'   Varnish
  • [Varnish] #314: undefined reference to `pthread_self'   Varnish
  • [Varnish] #314: undefined reference to `pthread_self'   Varnish
  • [Varnish] #314: undefined reference to `pthread_self'   Varnish
• [Varnish] #290: Make dir in /usr/local/var/varnish   Varnish
• [Varnish] #315: assertion in STP_LOOKUP   Varnish
  • [Varnish] #315: assertion in STP_LOOKUP   Varnish
  • [Varnish] #315: assertion in STP_LOOKUP   Varnish
  • [Varnish] #315: assertion in STP_LOOKUP   Varnish
  • [Varnish] #315: assertion in STP_LOOKUP   Varnish
  • [Varnish] #315: assertion in STP_LOOKUP   Varnish
  • [Varnish] #315: assertion in STP_LOOKUP   Varnish
• [Varnish] #316: varnishtest should mkdtemp or similar for its varnishd testing directory   Varnish
  • [Varnish] #316: varnishtest should mkdtemp or similar for its varnishd testing directory   Varnish
  • [Varnish] #316: varnishtest should mkdtemp or similar for its varnishd testing directory   Varnish
• [Varnish] #254: Condition(oe2->timer_when >= oe->timer_when) not true   Varnish
• [Varnish] #55: varnish stops responding with apache keepalive On   Varnish
• [Varnish] #61: Varnish -> Apache httpd mod_rewrite : 7 seconds delay   Varnish
  • [Varnish] #61: Varnish -> Apache httpd mod_rewrite : 7 seconds delay   Varnish
• [Varnish] #302: Varnishstat: % of caching: Bytes actually sent VS bytes sent with no cache   Varnish
• [Varnish] #273: running out of virtual memory on 32 bit server   Varnish
  • [Varnish] #273: running out of virtual memory on 32 bit server   Varnish
  • [Varnish] #273: running out of virtual memory on 32 bit server   Varnish
• [Varnish] #204: Handling of HTTP headers   Varnish
• Varnish crashing excessivly   Erik Jansson
  • Varnish crashing excessivly   Tollef Fog Heen
• [Varnish] #317: Assert error in cnt_lookup(), cache_center.c line 618:   Varnish
  • [Varnish] #317: Assert error in cnt_lookup(), cache_center.c line 618:   Varnish
• [Varnish] #295: Varnishd using all available memory, even using limited malloc   Varnish
  • [Varnish] #295: Varnishd using all available memory, even using limited malloc   Varnish
  • [Varnish] #295: Varnishd using all available memory, even using limited malloc   Varnish
  • [Varnish] #295: Varnishd using all available memory, even using limited malloc   Varnish
  • [Varnish] #295: Varnishd using all available memory, even using limited malloc   Varnish
  • [Varnish] #295: Varnishd using all available memory, even using limited malloc   Varnish
• [Varnish] #275: Varnish child stops responding   Varnish
  • [Varnish] #275: Varnish child stops responding   Varnish
  • [Varnish] #275: Varnish child stops responding   Varnish
  • [Varnish] #275: Varnish child stops responding   Varnish
  • [Varnish] #275: Varnish child stops responding   Varnish
  • [Varnish] #275: Varnish child stops responding   Varnish
  • [Varnish] #275: Varnish child stops responding   Varnish
  • [Varnish] #275: Varnish child stops responding   Varnish
  • [Varnish] #275: Varnish child stops responding   Varnish
• [Varnish] #217: varnishtop freeze   Varnish
• [Varnish] #280: Workspace overflows give confusing error messaqe   Varnish
• [Varnish] #284: Child [] Panic message: Assert error in VRT_r_server_ip(), cache_vrt.c line 476   Varnish
  • [Varnish] #284: Child [] Panic message: Assert error in VRT_r_server_ip(), cache_vrt.c line 476   Varnish
• [Varnish] #279: varnishlog init file does not work   Varnish
  • [Varnish] #279: varnishlog init file does not work   Varnish
• [Varnish] #223: fixed redhat varnishlog init script and added one for varnishncsa   Varnish
  • [Varnish] #223: fixed redhat varnishlog init script and added one for varnishncsa   Varnish
  • [Varnish] #223: fixed redhat varnishlog init script and added one for varnishncsa   Varnish
• [Varnish] #190: VCL Sample   Varnish
• [Varnish] #318: Bug when 302 redirect used on ESI page   Varnish
  • [Varnish] #318: Bug when 302 redirect used on ESI page   Varnish
• [Varnish] #278: Backend connection does not timeout   Varnish
• [Varnish] #268: Make 304 and Last-Modified work with ESI   Varnish
• [Varnish] #265: Implement nuke option to invalidate all variants of an object   Varnish
• [Varnish] #259: support for revalidating with 304, support for user-reloading   Varnish
• [Varnish] #319: VCL_error_method ,child exited on signal 6   Varnish
  • [Varnish] #319: VCL_error_method ,child exited on signal 6   Varnish
• [Varnish] #303: Description length in 2. column in varnishtop is too short   Varnish
• [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
  • [Varnish] #320: ESI fails with POST fails   Varnish
• [Varnish] #321: hild (4945) Panic message: Assert error in EXP_Touch(), cache_expire.c line 206:   Varnish
  • [Varnish] #321: hild (4945) Panic message: Assert error in EXP_Touch(), cache_expire.c line 206:   Varnish
• [Varnish] #322: PATCH: Enable mmap of devices if running Linux   Varnish
  • [Varnish] #322: PATCH: Enable mmap of devices if running Linux   Varnish
  • [Varnish] #322: PATCH: Enable mmap of devices if running Linux   Varnish
• [Varnish] #323: Remove tcl requirement to build   Varnish
  • [Varnish] #323: Remove tcl requirement to build   Varnish
• [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
  • [Varnish] #324: Full freeze   Varnish
• [Varnish] #325: assert bug error - trunk r3102   Varnish
  • [Varnish] #325: assert bug error - trunk r3102   Varnish
• [Varnish] #326: ESI with <esi starting off   Varnish
  • [Varnish] #326: ESI with <esi starting off   Varnish
• [Varnish] #266: Fix bug in ESI parser   Varnish
• [Varnish] #327: varnishd fails to parse config, reporting "Backend port '"8080"': Name or service not known"   Varnish
  • [Varnish] #327: varnishd fails to parse config, reporting "Backend port '"8080"': Name or service not known"   Varnish
  • [Varnish] #327: varnishd fails to parse config, reporting "Backend port '"8080"': Name or service not known"   Varnish
• [Varnish] #276: varnishd leaks fds and enters busy-loop   Varnish
  • [Varnish] #276: varnishd leaks fds and enters busy-loop   Varnish
  • [Varnish] #276: varnishd leaks fds and enters busy-loop   Varnish
  • [Varnish] #276: varnishd leaks fds and enters busy-loop   Varnish
  • [Varnish] #276: varnishd leaks fds and enters busy-loop   Varnish
• [Varnish] #328: 2.0-beta1 does not compile on OSX 10.4   Varnish
  • [Varnish] #328: 2.0-beta1 does not compile on OSX 10.4   Varnish
  • [Varnish] #328: 2.0-beta1 does not compile on OSX 10.4   Varnish
  • [Varnish] #328: 2.0-beta1 does not compile on OSX 10.4   Varnish
• [Varnish] #329: Increase cli_timeout   Varnish
  • [Varnish] #329: Increase cli_timeout   Varnish
  • [Varnish] #329: Increase cli_timeout   Varnish
• [Varnish] #330: 2.0-beta1 dies with accept error   Varnish
  • [Varnish] #330: 2.0-beta1 dies with accept error   Varnish
  • [Varnish] #330: 2.0-beta1 dies with accept error   Varnish
  • [Varnish] #330: 2.0-beta1 dies with accept error   Varnish
  • [Varnish] #330: 2.0-beta1 dies with accept error   Varnish
  • [Varnish] #330: 2.0-beta1 dies with accept error   Varnish
  • [Varnish] #330: 2.0-beta1 dies with accept error   Varnish
• Undelivered Mail Returned to Sender   Mail Delivery System
• [Varnish] #331: Varnish resends requests to backends after a restart   Varnish
  • [Varnish] #331: Varnish resends requests to backends after a restart   Varnish
• [Varnish] #332: Varnish should greet you with a greeting   Varnish
  • [Varnish] #332: Varnish should greet you with a greeting   Varnish
  • [Varnish] #332: Varnish should greet you with a greeting   Varnish
• [Varnish] #191: Varnish won't cache if apache keepalive is set to on   Varnish
• [Varnish] #333: VCL compilation commandline doesn't take account LDFLAGS   Varnish
  • [Varnish] #333: VCL compilation commandline doesn't take account LDFLAGS   Varnish
  • [Varnish] #333: VCL compilation commandline doesn't take account LDFLAGS   Varnish
  • [Varnish] #333: VCL compilation commandline doesn't take account LDFLAGS   Varnish
  • [Varnish] #333: VCL compilation commandline doesn't take account LDFLAGS   Varnish
  • [Varnish] #333: VCL compilation commandline doesn't take account LDFLAGS   Varnish
• [Varnish] #334: GLIBC asprintf() incompatibility   Varnish
• [Varnish] #335: varnishncsa patch: log X-Forwarded-For instead of clientip if it exists   Varnish
  • [Varnish] #335: varnishncsa patch: log X-Forwarded-For instead of clientip if it exists   Varnish
• [Varnish] #336: varnishlog writes garbage to file   Varnish
  • [Varnish] #336: varnishlog writes garbage to file   Varnish
• [Varnish] #337: varnish doesn't work if compiled as 64bit in MacOSX   Varnish
  • [Varnish] #337: varnish doesn't work if compiled as 64bit in MacOSX   Varnish
  • [Varnish] #337: varnish doesn't work if compiled as 64bit in MacOSX   Varnish
• [Varnish] #338: Enable kqueue on Darwin 9+   Varnish
  • [Varnish] #338: Enable kqueue on Darwin 9+   Varnish
• [Varnish] #339: Repeated Assert error in cnt_recv()   Varnish
  • [Varnish] #339: Repeated Assert error in cnt_recv()   Varnish
  • [Varnish] #339: Repeated Assert error in cnt_recv()   Varnish
• [Varnish] #340: Silent failure on config error when starting as a daemon in CentOS5.2   Varnish
  • [Varnish] #340: Silent failure on config error when starting as a daemon in CentOS5.2   Varnish
• [Varnish] #341: obj.valid is not recognized as a valid variable   Varnish
  • [Varnish] #341: obj.valid is not recognized as a valid variable   Varnish
  • [Varnish] #341: obj.valid is not recognized as a valid variable   Varnish
• [Varnish] #342: error keyword in vcl_fetch fails   Varnish

Last message date: Tue Sep 30 13:42:12 UTC 2008
Archived on: Wed Feb 11 18:00:08 UTC 2026

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...