andersb at vgnett.no
Tue Sep 12 21:55:53 CEST 2006
thx for the quick intro into the world of gdb today, it helped me make
varnishncsa more robust (found a cornercase).
In all modesty I think I can say that varnishncsa might be getting darn
close to alpha stage soon, but I am experiencing a major bug/designflaw
somewhere, that hopefully can be fixed pretty easily.
The result of this bug is something like this:
184.108.40.206 - - [12/Sep/2006:21:44:06 +0200 "GET
/grafikk/frontbilder/126179.jpg HTTP/1.1" 200 2532
"Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
1.1.4322; .NET CLR 2.0.50727)"
220.127.116.11 - - [12/Sep/2006:21:44:32 +0200 "" 0 0 "-" "-"
Notice that varnishsncsa halted for 26 seconds. So something in the SHM
loglines I read, is causing major problems for the logger.
The only way to fix it is to dump out varnishlog at the same time I run
varnishncsa and compair notes to see whats causing it.
This isn't a req for help, merly a state-of-code for varnishncsa.
Also, I will need a base64 decoder soon to make varnishncsa follow the
NCSA standard. How would we include this in Varnish DES? Is base64
decoding part of "standard" C? Or do we import the library, or do we cut
paste the BSD licensed base64 code?
More information about the varnish-dev