Ok, I found the bug. I'll compile a beta3-1 for the client.
[EMAIL PROTECTED] wrote:
table rotation is good. Originally I pondered about an archive mode. I.e. a periodical "insert into log_archive" done by the newpki_daemon, e.g. every 2 days, and "log_archive" as a parallel table to "logs". Then "log_archive" is under disposition to the user to delete from. Eventually when table "logs_archive" is not present, because dropped, no "insert into log_archive" takes place. In the inspection screen there could be a switch "logs" or "logs_archive".
-----Urspr�ngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Fr�d�ric Giudicelli Gesendet: Freitag, 23. Januar 2004 12:50 An: [EMAIL PROTECTED] Betreff: Re: AW: server-2.0.0-beta3 / problem in logging
[EMAIL PROTECTED] wrote:
status today (5 days newpki server running)
select count(*) from newpki_server.logs .. > 90.000 records select count(*) from REP_alpha.logs .. > 200.000 records
Well... mysql is supposed to handle up to 4 billions entries... :) But this will certainly become a problem at some point. Maybe I could do some table rotation, like every month rename "logs" and "logs_hash", recreate it empty, and save up to 4 months worth of logs.
-- Fr�d�ric Giudicelli http://www.newpki.org _____________________________________________________________________ NewPKI http://www.newpki.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
_____________________________________________________________________ NewPKI http://www.newpki.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
-- Fr�d�ric Giudicelli http://www.newpki.org _____________________________________________________________________ NewPKI http://www.newpki.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
