Message-ID: <555211E1.3010805@gmx.net>
Date: Tue, 12 May 2015 10:44:49 -0400
From: Peter Eisentraut <peter_e@gmx.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: pgsql-pkg-yum@postgresql.org
Subject: pgbouncer logrotate configuration
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-pkg-yum-owner@postgresql.org

The pgbouncer logrotate configuration seems a bit contradictory:

﻿﻿/var/log/pgbouncer.log {
    missingok
    notifempty
    sharedscripts
    copytruncate
    create 0640 pgbouncer pgbouncer
    nodateext
    postrotate
        /bin/kill -HUP `cat /var/run/pgbouncer/pgbouncer.pid
2>/dev/null` 2> /dev/null || true
    endscript
}

"create" is ignored if "copytruncate" is used.  And having a postrotate
script to send a HUP signal is also pointless if copytruncate is used.
We need to decide on one way to do it: either copytruncate, or rename
and SIGHUP.

It also seems to me that this might be a bit simpler if we created a
subdirectory /var/log/pgbouncer/ for all the log files.  Then we
wouldn't have the permissions issues that the "create" directory is
attempting to solve.

Comments?


-- 
Sent via pgsql-pkg-yum mailing list (pgsql-pkg-yum@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-yum