Re: udp logging in 2.HEAD
On Mon, Sep 24, 2007, Henrik Nordstrom wrote: > On m??n, 2007-09-24 at 00:23 +0800, Adrian Chadd wrote: > > > * tune the udp buffer size rather than having it fixed - you could > > in theory fire off 32k UDP packets if your receive side would > > handle them fine. Thats ~200 logging entries each UDP packet. > > You could, if you like fragmented IP packets.. Thats no big deal; the big deal is if you run a lossy network your risk of losing logentries is higher with larger packets. I've not done more than cursory testing of this yet so I'm not sure what the impact will be of large volumes of small UDP packets or smaller volume of larger UDP packets are. Chalk one up for after exams. > > * Some debugging to indicate when things aren't going to plan. > > like? Connection refused at other end; socket write errors, etc. Just doing it every 30 seconds or so rather than on every write. > > * Some application notes or documentation. :0 > > You mean squid.conf notes, or something else? Yup, and a Faq entry for it. Adrian
Re: udp logging in 2.HEAD
On mån, 2007-09-24 at 00:23 +0800, Adrian Chadd wrote: > * tune the udp buffer size rather than having it fixed - you could > in theory fire off 32k UDP packets if your receive side would > handle them fine. Thats ~200 logging entries each UDP packet. You could, if you like fragmented IP packets.. > * Some debugging to indicate when things aren't going to plan. like? > * Some application notes or documentation. :0 You mean squid.conf notes, or something else? Regards Henrik signature.asc Description: This is a digitally signed message part
Re: udp logging in 2.HEAD
On Sun, Sep 23, 2007, Adrian Chadd wrote: > G'day, > > I've committed a version of the patch Tim Starling (Wikipedia) wrote > to squid-2.HEAD. It -almost- works; I'm seeing lines like this: > > > 1190560927.196 4526 192.168.1.7 TCP_MISS/504 317 GET > http://192.168.1.7:8080/w10953a8c.27fa10d3:0006/t01/_1190560927.196 > 2848 192.168.1.7 TCP_MISS/504 317 GET > http://192.168.1.7:8080/w10953a8c.27fa10d3:0006/t01/_010c - > DIRECT/192.168.1.7 text/html And thats just netcat being stupid under FreeBSD and having a default frame size of 1k. Stupid, stupid me. UDP logging works fine; what would be nice: * tune the udp buffer size rather than having it fixed - you could in theory fire off 32k UDP packets if your receive side would handle them fine. Thats ~200 logging entries each UDP packet. * Some debugging to indicate when things aren't going to plan. * Some application notes or documentation. :0 Adrian
