I just installed this on a client's site that has 15,000 active users on right now. ya, there is a few bots :P

he's use to real users being between 8,000 and 14,000 but its been constant at 15k now and we are trying new things.

like this..

:)

now 1 issue i just discovered is your logs table can grow fast and you have no hook_cron() implementation.

Is this in the plans? I could use that ASAP.

I'd see it where you'd have a config option to supply the max time a log entry can stay in the database and cron just simply deletes all that are => .

whatcha think?

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Title: Cron - Clean Logs Table » Add an 'expire old log entries' option and implement badbehavior_cron()
Version: 5.x-2.0-beta1 » 6.x-1.x-dev
dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Actually, I'd really like to see if we could somehow re-use the watchdog table for badbehavior logging.

Benj’s picture

Benj commented

Either of those ideas is good. We need something like that. I was just looking at a database and half it's size (100mib) is the bad_behavior_log (42mib). I'm a little relieved though - lol - I was wondering how my database dumps were growing so fast.

gregarios’s picture

gregarios commented
Version: 6.x-1.x-dev » 6.x-2.x-dev
Status: Active » Postponed

The log entries are deleted after 7 days, currently. It is hard-coded into the BB Scripts version 2.13 (and presumably above) and outside of the reach of the Drupal module. All I'd be able to do is reduce that limit further. In light of this, I'm marking this thread as postponed. however, I am ready to implement a setting for it when the ability becomes more useful and/or the hard limit is changed.

gregarios’s picture

gregarios commented
Status: Postponed » Closed (won't fix)