Thanks Lennart for replying. If I get you correctly we can hit this issue for both of the below cases 1. Reloading unit file via daemon-reload while the services are executing and 2. Services are active and we try to disable or mask a service without stopping it?
I apologize if I sound too repetitive. Upgrading my linux distribution (with latest systemd) will take some time. So trying to check if someway I can change the way I am using systemd to bypass this issue. On Tue, May 19, 2020 at 9:32 PM Lennart Poettering <lenn...@poettering.net> wrote: > > On Di, 19.05.20 20:47, Debraj Manna (subharaj.ma...@gmail.com) wrote: > > > Thanks Michael for replying and giving me the issue details. > > > > I am trying to understand in what scenarios we may hit this issue. I > > checked the issue. It states that "This can happen when the > > configuration is changed and reloaded while we are executing a > > service.". Can you also please explain what does configuration changed > > and reloaded mean? > > > > Does it mean doing some changes in systemd unit file and then > > re-loading (via daemon-reload) it while the services are executing or > > the services are active and we are trying to disable or do a mask > > operation? > > Yes. > > Lennart > > -- > Lennart Poettering, Berlin _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
