serendipity_spamblocklog

Random stuff about serendipity. Discussion, Questions, Paraphernalia.
Post Reply
jaal
Regular
Posts: 63
Joined: Thu Oct 26, 2006 2:48 pm
Location: Guetersloh, Germany
Contact:

serendipity_spamblocklog

Post by jaal »

Hi,

is there any way to deal automatically with the serendipity_spamblocklog table?
I'm currently moving to a bigger server and noticed that the serendipity_spamblocklog table does take over 150MB on the disk (and is still growing...)

Is there any switch to disable the writing to the database or an automatic retention time?

Thanks
Jan

P.S.: When the import is finished I will let you know how many entries are in the table...
Harald Weingaertner
Regular
Posts: 474
Joined: Mon Mar 27, 2006 12:32 am

Post by Harald Weingaertner »

What about configuring the Spam-Protection Event Plugin? The second last entry should be set to "No logging" (or whatever it is called in english) ;)

I have disabled the logging and everything is fine...

PS:
Protokollierung von fehlgeschlagenen Kommentaren
Die Protokollierung von fehlgeschlagenen Kommentaren und deren Gründen kann auf mehrere Arten durchgeführt werden.
(sprichst ja scheinbar deutsch)
jaal
Regular
Posts: 63
Joined: Thu Oct 26, 2006 2:48 pm
Location: Guetersloh, Germany
Contact:

Post by jaal »

I knew there was something about not seeing the forest for the trees...


I'll give it a try. The db file is currently about 900 MB and still growing...

Thanks
Jan
jaal
Regular
Posts: 63
Joined: Thu Oct 26, 2006 2:48 pm
Location: Guetersloh, Germany
Contact:

Post by jaal »

Just for the record: I killed the import after 2 hourse and > 2 Million lines...

Even the log can be disabled maybe there should be automatic retention time added.

Jan
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Post by garvinhicking »

Hi!
Even the log can be disabled maybe there should be automatic retention time added.
We follow the thought that if people enable logging, they want to log everything. So users should decide when to purge their logs. If they don't need logging, or need special retention times, they can use file logging and logrotate on the server's system.

Adding retention checks in a web application just leads to performance slowdowns, because on every pagerequest you'd have a query that would need to purge old records.

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Post Reply