http://qa.mandrakesoft.com/show_bug.cgi?id=6258
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2003-11-19 18:47 -------
Merged in jabber-1.4.3-1mdk.
thanks.
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
I've got a request for jabber package : provide support for logrotate.
Indeed I was unable to start my local jabber server until I understand
that the problem's comes from /var/log/jabber/record.log and
/var/log/jabber/error.log .
error.log grow, and grow so much that at the end
jabber doesn't want to start as error.log was too big ( more than 7Mo,
maybe kopete related ... ). This limitation comes from xdb component.
So adding a script in /etc/logrotate.d could did the trick and allow to
don't have a jabber server stopping running at all ( this is limit a DoS
against jabber ).
weekly rotations should be enough with 4 copies for record.log, and
rotation when filesize exceed 1M should be enough for error.log :
/var/log/jabber/record.log {
monthly
rotate 4
notifempty
missingok
}
/var/log/jabber/error.log {
size=1M
rotate 4
notifempty
missingok