[Date Prev][Date Next]
Disk exhausting because of log.0000xxxx files
- To: email@example.com
- Subject: Disk exhausting because of log.0000xxxx files
- From: Olivier Nicole <Olivier.Nicole@cs.ait.ac.th>
- Date: Thu, 3 Sep 2009 13:00:21 +0700 (ICT)
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.ait.ac.th; h= subject:subject:from:from:message-id:date:date:received:received :received; s=selector1; t=1251957624; x=1253772024; bh=EP1+7xX2+ lQqhRhWIL12w1PLEEUp6ypmZPq6Dm5z1Kw=; b=Nd3TGmt3s0hWd6+SfOU9GwSad ykYaS60diGHaJLk1jvKrDvKA9gjUinHlALayDJMYCQiEAYCW7cx3z8lBHdseVrRY lPgZPZm8yUOnKH7U6KFkbqT0gRQt6lDa47I0fs19F4VFRQwJn9X/8H2jdGCURbUk Ykvc6CYPxIXPJtBFK0=
Because of a sputid script I wrote that was unduly modifying my LDAP
directory, I endup exhausting my disk space with Berkeley DB log files
of the type log.00000xxxx.
My LDAP uses a database of type bdb, I have the option
dbconfig set_flags DB_LOG_AUTOREMOVE
and thought it would take care of removing the log files. It seems not
so I must be missing something.
(As for back-up safety, I have a script that does a slapcat every 2
hours keeping 10 days of back-ups, plus nightly back-up on a back-up
server, so removing BDB logs should be quite safe)
Any help will be warmly welcome.