On Fri, 8 Oct 2004, John Young wrote: > >> # If a specific user session accesses our catalog more than this many > >>times > >>-# in a 30-second time period. If the limit is exceeded, the LockoutCommand > >>+# without a 30-second pause. If the limit is exceeded, the LockoutCommand > >> # (if set) is executed. Set this to 0 if you're getting links to 127.0.0.1 > >> # during your testing. > >> RobotLimit 100 > > > > > > Hmm. That seems to obscure the situation rather than clarify it, to me. > > Okay, how about: > "with no pauses of 30 seconds or more. If the limit..." > > Now, for further obscurity: > > The problem is the current description in catalog.cfg is wrong (not simply > confusing). Take another look at the code in Dispatch.pm. It doesn't > average > anything. It only checks to see if the current time minus the last session > write time is greater than 30: Ok, that makes sense. I just committed an update that follows your suggestion. Thanks! Jon -- Jon Jensen End Point Corporation http://www.endpoint.com/ Software development with Interchange, Perl, PostgreSQL, Apache, Linux, ... _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.