From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
---|---|
To: | pgsql-pkg-yum(at)postgresql(dot)org |
Subject: | Re: Reloading pgbouncer and systemd |
Date: | 2016-03-30 12:16:41 |
Message-ID: | 20160330141641.61f28755@firost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-yum |
Le Mon, 22 Feb 2016 17:38:45 +0100,
Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> a écrit :
> Hello,
>
> While working with pgbouncer under CentOS7, I noticed an incompatibility
> between pgbouncer and systemd when reloading.
>
> The current reload command is:
>
> ExecReload=/usr/bin/pgbouncer -R -q ${BOUNCERCONF}
>
> But this command create a new pgbouncer process...and keeps it in foreground.
> As the service type is set as "forking", in this situation systemctl just sits
> and wait for a return code (maybe there's a timeout, but I did not have the
> patience to wait for it).
>
> Either add a '-d' to this command, or send a HUP signal to the process.
>
> I prefer the second option as it doesn't create a new process that takes over
> the sockets, but just reloads the conf file as expected. Much lighter.
>
> So, imho, the pgbouncer.service file should have:
>
> ExecReload=/bin/kill -HUP $MAINPID
Any feedback on this ?
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim Gündüz | 2016-03-30 12:32:09 | Re: New releases are due on Thursday |
Previous Message | Jeff Frost | 2016-03-29 14:52:57 | Re: New releases are due on Thursday |