On Mon, 18.05.15 07:51, Igor Bukanov (i...@mir2.org) wrote: > On 18 May 2015 at 05:35, Andrei Borzenkov <arvidj...@gmail.com> wrote: > > > > > > What exactly do you mean? It has RefuseManualStart set? > > I meant that, for example, A is enabled and contains Requires=B and > this is the only dependency that causes B to run and then B alters or > even disables A and calls systemctl daemon-reload. > > > I'm not entirely sure what systemd can sensibly do in this case though. > > What I would like to know is what is the exact behavior of systemctl > daemon-reload. I am writing a service that creates/modifies other > units by placing files under /run and I would like to know what are > the limitations. In my case I cannot use a systemd.generator as the > service depends on a mounted directory.
Well, my recommendation is to avoid daemon-reloads during the normal boot process if possible, since there are some unresolved issues: If you run a service with multiple ExecStart= lines, we currently do not remember at which one we are while doing a daemon reload (simply because it's not clear how to solve this comprehensively: should we go by line number or should we search for the same command line? -- after all the precise set of ExecStart= lines might have changed due to the reload). Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
