On 11/27/2014 06:37 AM, Stig Sandbeck Mathisen wrote:
> Gaudenz Steinlin <gaud...@debian.org> writes:
>
>> I'll try to find some time to have a look, but can't promise anything.
>
> Adding the following files fixed this issue for me:
>
> head /etc/tmpfiles.d/*
> ==> /etc/tmpfiles.d/ceilometer.conf <==
> d /run/ceilometer 0755 ceilometer ceilometer - -
>
> ==> /etc/tmpfiles.d/glance.conf <==
> d /run/glance 0755 glance glance - -
>
> ==> /etc/tmpfiles.d/keystone.conf <==
> d /run/keystone 0755 keystone keystone - -
>
> Packages will normally install these files into /usr/lib/tmpfiles.d/
> instead.
>
> If the packages:
>
> * contain the file debian/packagename.tmpfile with content described
> above.
>
> * is built using debhelper with dh_systemd (I see this is true for the
> "keystone" package)
>
> ...this will create the run directories when the packages are installed,
> as well as on boot, and then only if systemd is running as pid 1.
I'm not sure I understand what you're proposing as a fix. And it's a
shame, because it seems you have the correct solution. Could you try to
explain again what we should do? Should each daemon contain a new file
in /etc/tmpfiles.d?
So, if I understand well, simply modifying
init-template/pkgos-gen-systemd-unit in openstack-pkg-tools and adding
what's below, would fix the issue:
TMP_FILE=`echo ${INIT_TEMPLATE} | sed 's/.init.in/.tmpfile/'`
echo "d /run/${PROJECT_NAME} 0755 ${PROJECT_NAME} ${PROJECT_NAME} - -" \
>${TMP_FILE}
Please confirm the above is correct, because that's the first time I
hear about the .tmpfile thing. Also, if we do this, should we remove the
RuntimeDirecotry directive from the .service generated files?
Cheers,
Thomas Goirand (zigo)
P.S: Guys, please do not CC the bug *and* the list, as we would
otherwise all receive the mail twice...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
