On 12/02/2016 00:34, Patrick Boutilier via Info-cyrus wrote:
It fits because your Cyrus is configured to use BerkleyDB for some 9or
all) of the databases.
You should not have to stop Cyrus. Running this command (with proper -h
location) should show you what log files are no longer used:
db_arch
It fits because your Cyrus is configured to use BerkleyDB for some 9or
all) of the databases.
You should not have to stop Cyrus. Running this command (with proper -h
location) should show you what log files are no longer used:
db_archive -h /var/imap/db
And this command should get rid of th
On 10/02/2016 9:08 AM, Patrick Boutilier via Info-cyrus wrote:
Not sure if Cyrus is supposed to clean up (been using skiplist
exclusively for years now) but according to this link you can remove the
old log files.
http://www-rohan.sdsu.edu/doc/BerkeleyDB/ref/transapp/logfile.html
How does tha
Not sure if Cyrus is supposed to clean up (been using skiplist
exclusively for years now) but according to this link you can remove the
old log files.
http://www-rohan.sdsu.edu/doc/BerkeleyDB/ref/transapp/logfile.html
On 02/09/2016 04:05 PM, Carl Brewer via Info-cyrus wrote:
I asked this a
I asked this a few months ago, but now it's getting urgent. I have a
NetBSD 5.x server, running Cyrus imapd 2.4.17 from pkgsrc, /var/imap/db
is getting very full :
bash-4.3# du -sh db
7.0Gdb
(this is on a reasonably small server)
and it grows every day, it's full of these :
-rw---
