> > I hope to hear from you regarding the gettimeofday thing, and if this was
> > not relevant as expected.
> >
>
> Indeed it looked to be bogus - taking it out, it ran for ~8 hours,
> answered 8257845 queries before it ran out of queries in my test set,
> no apparent problems. I've just set it off to check again, then I'll
> try it in a real environment. This is the patch:
>
I've run another 8M queries through it in a test environment, and put
it onto a live box where its been up for 5 hours, answered over a
million queries and I've not seen a problem, so I'm hoping that this
is the right fix. Certainly I've not managed to see it running live
for anything like this long previously.
So we're clear - this is the patch I've been doing this testing with:
Index: pdns-recursor/portsmplexer.cc
===================================================================
RCS file: /cvsroot/upstream/pdns-recursor/portsmplexer.cc,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 portsmplexer.cc
--- pdns-recursor/portsmplexer.cc 12 Nov 2006 16:56:13 -0000 1.1.1.1
+++ pdns-recursor/portsmplexer.cc 13 Sep 2007 06:34:36 -0000
@@ -94,7 +94,7 @@
if(ret < 0 && errno!=EINTR && errno!=ETIME)
throw FDMultiplexerException("completion port_getn returned
error: "+stringerror());
- if((ret < 0 && errno==ETIME) || numevents==0) // nothing
+ if((ret < 0 && errno==EINTR) || numevents==0) // nothing
return 0;
d_inrun=true;
--
Alex Kiernan
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
