I recently deployed jabberd2.2.17 on my local machine with a BerkeleyDB backend. I noticed that, even when only used with a test account, the local db folder contains a log that can potentially become large (output of my var/db folder): -rw-r----- 1 jabber jabber 20K Jul 7 17:36 authreg.db -rw-r----- 1 jabber jabber 24K Jul 7 17:39 __db.001 -rw-r----- 1 jabber jabber 192K Jul 7 17:39 __db.002 -rw-r----- 1 jabber jabber 264K Jul 7 17:39 __db.003 -rw-r----- 1 jabber jabber 160K Jul 7 17:39 __db.004 -rw-r----- 1 jabber jabber 552K Jul 7 17:39 __db.005 -rw-r----- 1 jabber jabber 40K Jul 7 17:38 __db.006 -rw-r----- 1 jabber jabber 10M Jul 7 17:38 log.0000000001 -rw-r----- 1 jabber jabber 152K Jul 7 17:36 sm.db As I am running this server on an SSD, I'd like to disable all logging. I changed all configuration files to output their logs to /dev/null, but the log.000000001 keeps popping up. Is there any way to disable this default behavior? (I take it that BerkeleyDB does the rotation himself, but not the removal of old db logs?) Thanks in advance!
