[systemd-devel] binding tmpfiles.d to unit startup

[Michael Biebl]

2014-03-01 20:18 GMT+01:00 Tom Gundersen <teg at jklm.no>:
> On Sat, Mar 1, 2014 at 8:04 PM, Michael Biebl <mbiebl at gmail.com> wrote:
>> 2014-03-01 19:47 GMT+01:00 Colin Walters <walters at verbum.org>:
>>> On Sat, Mar 1, 2014 at 1:44 PM, Michael Biebl <mbiebl at gmail.com> wrote:
>>>
>>> I vaguely remember that we exactly had this discussion a while ago.
>>>
>>>
>>> Argh, yes, possibly. The dangers of getting older...
>>>
>>> Unfortunately I'm not able to find it in the archives right now.
>>
>> Found it: http://lists.freedesktop.org/archives/systemd-devel/2013-July/011956.html
>
> And a bit further down that thread there was this proposal from Lennar
> (which doesn't seem far from what Colin wants):
> <http://lists.freedesktop.org/archives/systemd-devel/2013-July/012024.html>.

In Debian we have debhelper addons which generate maintainer scripts
code automatically to run systemd-tmpfiles
/usr/lib/tmpfiles.d/foo.conf upon installation, so this isn't really a
problem anymore for us.

Regarding discoverability, my suggestion in that thread was to add a
new field which allows to reference the associated tmpfiles snippet,
similar as we do for Documentation.

Having such a reference on the tmpfile snippet(s) in the .service file
would also make it possible to run them automatically whenever the
service is started. This could be useful for distros which haven't
automated the invocation of systemd-tmpfiles

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?