On Thu, 06.08.15 12:38, Reindl Harald ([email protected]) wrote: > Am 06.08.2015 um 12:16 schrieb Lennart Poettering: > >On Thu, 06.08.15 10:57, Reindl Harald ([email protected]) wrote: > > > >>>So, you'll get this EEXIST error only if there's already something at > >>>the place of the runtime dir that is either: > >> > >>NOBODY but systemd creates that directory > >>it don't exist at all before the service is started > >> > >>the problem is that SOMETIMES at stop is > >>seems not to be removed and so the next start > >>fails > > > >Whether it is removed or not should not matter really, the code is > >completely fine already exists as long as the uid/gid/mode match (as > >mentioned before). > > no, the code is *not* fine > > "Failed at step RUNTIME_DIRECTORY spawning" for the *ExecStartPost* in > nonsense since it is already created *before* ExecStart
See: https://github.com/systemd/systemd/pull/896 Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
