| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Cc: | pgsql-pkg-yum(at)postgresql(dot)org |
| Subject: | Re: pgbouncer systemd does not work on CentOS 7 |
| Date: | 2015-09-22 18:52:27 |
| Message-ID: | 5601A36B.5070404@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-yum |
On 5/15/15 4:04 PM, Peter Eisentraut wrote:
> On 5/12/15 5:26 PM, Devrim Gündüz wrote:
>>> I think the systemd configuration is faulty. It currently reads
>>>
>>> [Service]
>>> Type=forked
>>>
>>> ...
>>>
>>> ExecStart=/usr/bin/pgbouncer -d -v ${BOUNCERCONF}
>>>
>>> If I change that to
>>>
>>> [Service]
>>> Type=simple
>>>
>>> ...
>>>
>>> ExecStart=/usr/bin/pgbouncer -v ${BOUNCERCONF}
>>>
>>> it works
>>>
>>> Alternatively, the first version can be made to work by adding
>>> RemainAfterExit=yes.
>>>
>>> But clearly, the second version is more in line with the systemd philosophy.
>>
>> Thanks for the report. I picked up second way, and committed to git.
>
> Why? Wouldn't the non-forking approach be more in line with what
> systemd expects?
ping
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim GÜNDÜZ | 2015-09-22 20:19:03 | Re: pgbouncer systemd does not work on CentOS 7 |
| Previous Message | Peter Eisentraut | 2015-09-22 18:51:53 | Re: pgbouncer logrotate configuration |