Dave Emory wrote: > Daniel L. Miller wrote: >>>>>>>> I may have perhaps found the answer. My >>>>>>>> exportExtremeFileAppend was checked, and the exportextreme file >>>>>>>> was ... a trifle large. A "sort -u" shrunk it to a manageable >>>>>>>> size, and ASSP is blocking connections again. > > Hi, perl people. > > I'm a bit concerned that the large file caused ASSP to misbehave. I'm no > perl wizard, but a quick look at the code seems to show that ASSP builds a > regex containing the bad IP addresses. I think that means the regex is in > memory. Is there some kind of size limit on a regex in memory (other than > physical memory)? Are any other regexes at risk for getting too large? If > I'm totally wrong about how the exported extreme file is used, please think > about what would go wrong if it's large.
For the record, ASSP loads everything into memory. It only checks for changes and flushes the files back to disk as needed. The reason the file grew so large, i believe, is because of the append setting. It took around 700,000 IPs to reach a file size of 10MB according to my tests here, thats a bit overzealous if you ask me. That aside, Daniel has demonstrated that the large file size is NOT the issue at hand, so it's not much of an issue as far as i see it. Kevin ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
