On Mon, May 18, 2015 at 8:51 AM, 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. >
In this case stopping B would be a bug. "Requires" dependency is only ever considered when you start unit. But B could have been started manually, so stopping it would be wrong. >> 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. As I already said, daemon-reload should not trigger any unit state change itself. But I do not think it is set as documented API anywhere. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel