[PKG-Openstack-devel] Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

[Gaudenz Steinlin]

Hi

I did not look into this praticular problem yet, but just a few comments
from my experience with converting other packages to systemd.

Stig Sandbeck Mathisen <ssm at debian.org> writes:

> Looks like my proposed solution (RuntimeDirectory=) does not work very
> well with multiple services needing the same /run/something directories.
>
> When I defined multiple services with the same RuntimeDir=, the services
> delete each others runtime directories. This is documented in
> systemd.exec(5) for RuntimeDirectory=. This affects the ceilometer-* and
> glance-* services.

Could this be handled with proper dependencies between these services?
To ensure that the directory is already created?

>
> The processes are started, but since pidfiles are not created, and the
> systemd units are configured with PIDFile=, systemd times out waiting
> for the pidfiles to be created, and assumes the services didn't start
> correctly, which again the packages from being installed.

Why do you set PIDFile at all? IMO pidfiles are unnecessary when the
daemons managed by systemd run in the foreground and thus there is no
need for a pidfile at all.

>
> I'll try using "tmpfiles.d" to solve this, as the systemd.exec(5) man
> page already mentions.

Sounds good too, but like a lot of effort just to support legacy pid
files (iff that's the only reasons for these directories).

Gaudenz