On 19 May 2015 at 12:08, Lennart Poettering lenn...@poettering.net wrote:
On Tue, 19.05.15 08:22, Igor Bukanov (i...@mir2.org) wrote:
In any case, I thought that if I add
a dependency like After=my-config-is-ready.target for most default
services that can be configured, load a config from a
On Sun, 17.05.15 10:06, Igor Bukanov (i...@mir2.org) wrote:
Hello,
suppose a unit B runs just because another unit A contains Requires=B and
After=B. When B runs, it changes A like adding new dependencies, altering
Exec command etc and then B calls systemctl daemon-reload. Then the systemd
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
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
On 18 May 2015 at 17:18, Lennart Poettering lenn...@poettering.net wrote:
Well, my recommendation is to avoid daemon-reloads during the normal
boot process if possible, since there are some unresolved issues:
What is then a canonical way to implement initialization when the
configuration comes
On Mon, 18.05.15 17:53, Igor Bukanov (i...@mir2.org) wrote:
On 18 May 2015 at 17:18, Lennart Poettering lenn...@poettering.net wrote:
Well, my recommendation is to avoid daemon-reloads during the normal
boot process if possible, since there are some unresolved issues:
What is then a
Le lundi 18 mai 2015, 07:51:18 Igor Bukanov a écrit :
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
Hello,
suppose a unit B runs just because another unit A contains Requires=B and
After=B. When B runs, it changes A like adding new dependencies, altering
Exec command etc and then B calls systemctl daemon-reload. Then the systemd
uses the new definition for A, right?
In particular, if according
В Sun, 17 May 2015 10:06:28 +0200
Igor Bukanov i...@mir2.org пишет:
Hello,
suppose a unit B runs just because another unit A contains Requires=B and
What exactly do you mean? It has RefuseManualStart set?
After=B. When B runs, it changes A like adding new dependencies, altering
Exec
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
10 matches
Mail list logo
