Re: RHEL7 pgbouncer package /run/pgbouncer rights glitch after reboot

> On May 14, 2015, at 2:42 AM, Laurent Wandrebeck <l(dot)wandrebeck(at)quelquesmots(dot)fr> wrote:
>
>
> Laurent Wandrebeck <l(dot)wandrebeck(at)quelquesmots(dot)fr <mailto:l(dot)wandrebeck(at)quelquesmots(dot)fr>> a écrit :
>
>> Hi,
>>
>> I’d like to report a small problem with latest pgbouncer package(1.5.5-1.rhel7).
>>
>> /var/run being tmpfs, /var/log/pgbouncer becomes root:root after a
>> reboot, thus pgbouncer fails to start, being unable to write its pid
>> file.
>>
>> I’ve done a quick search to find where to change it at boot, and I
>> stumbled upon prosody package, whose /run/prosody is ok.
>>
>> The package contains:
>> # cat /usr/lib/tmpfiles.d/prosody.conf
>> d /run/prosody 755 prosody prosody
>>
>> Hope it helps for 1.5.5-2.rhel7 :)
>>
>> Keep up the good work,
>>
>> Best,
>> Laurent.
>
> Replying to myself after willing to fix it there…
>
> There’s already a /usr/lib/tmpfile.d/pgbouncer.conf
> but it’s content is a bit borked, /var/run/pgbouncer/pqbouncer (yes, twice).
> There we have the culprit :)

Looks like that’s this bit here in the spec file:

%global _varrundir %{_localstatedir}/run/%{name}

<SNIP>

# ... and make a tmpfiles script to recreate it at reboot.
%{__mkdir} -p %{buildroot}%{_tmpfilesdir}
cat > %{buildroot}%{_tmpfilesdir}/%{name}.conf <<EOF
d %{_varrundir}/pgbouncer 0700 pgbouncer pgbouncer -
EOF

I’m thinking the intent would be this:

d %{_varrundir} 0700 pgbouncer pgbouncer -

but just want Devrim to have a chance to comment.