>> heh... it all depends from how you set up things; either use a >> shorter expiry for traps which will STILL help you in case of heavily >> targeted addresses (and wich will avoid having a too big list) *or* >> move the whole to a database (even a BerkeleyDB one) so you won't >> need to "load" the whole blurb in memory; in either case the trap >> *has* its "raison d'etre" imHo
> We are talking here ASSP V1. Ok, yet, keeping the "pbtraps" option (and allowing to disable it if needed) makes sense, and lowering the "lifetime" for entries will help btw; heavy "bombed" addresses will stay in cache while others will be discarded (and eventually recreated) from time to time... but btw that's up to you ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
