Yes, it reopens a new logfile upon SIGHUP. This is what's needed in the logrotate conf file: postrotate /bin/kill -HUP `cat <dbfarm>/merovingian.pid 2>/dev/null` 2> /dev/null || true endscript On 3 March 2017 at 16:17, Roberto Cornacchia wrote:

To make it work with logrotate, does it need to be sent a SIGHUP?

On 3 March 2017 at 16:06, Martin Kersten wrote:

...

Sure, just create a cron-job to mv it aside and compress it, or simple discard.

On 03/03/2017 15:59, Roberto Cornacchia wrote:

...

Is there a way to make monetdbd a bit quieter? In a setting with many connections, it quickly becomes several GB of this:

2016-03-01 10:25:03 MSG merovingian[94243]: proxying client localhost:52272 for database 'xxx' to mapi:monetdb:///var/lib/monetd b/dbfarms/yyy/xxx/.mapi.sock?database=xxx 2016-03-01 10:25:03 MSG merovingian[94243]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying

_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list