>>> Lennart Poettering schrieb am 22.08.2019 um 16:19
>>> in
Nachricht <20190822141902.GA585@gardel-login>:
[...]
> Ahum, this change is a single line added to a default sysct.d/ file we
> ship. I mean, you may have your opinions, but this line is not applied
> in PID 1 at all, it doesn't touch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 26.08.19 um 00:19 schrieb Hans-Dieter Doll:
> There are also interactive applications started as user sessions.
> Some of these must not be killed but terminated by the supervisor,
> otherwise we (i.e. our customers) run into trouble.
>
> Wit
Am 25.08.19 um 22:02 schrieb Andrei Borzenkov:
> 25.08.2019 19:57, Hans-Dieter Doll пишет:
>> On shutdown we need to stop a service before systemd begins to kill all
>> processes it does not know.
>> The service is a process supervisor similar to init, which controls all our
>> applications.
>> O
25.08.2019 19:57, Hans-Dieter Doll пишет:
> On shutdown we need to stop a service before systemd begins to kill all
> processes it does not know.
> The service is a process supervisor similar to init, which controls all our
> applications.
> Our applications must be terminated by this supervisor,
On shutdown we need to stop a service before systemd begins to kill all
processes it does not know.
The service is a process supervisor similar to init, which controls all our
applications.
Our applications must be terminated by this supervisor, otherwise data loss and
inconsistencies will occur
On Mon, 19 Aug 2019 at 14:38, Steve Dodd wrote:
[..]
> if I start it with systemctl start systemd-nspawn@name, all works as
> expected.
>
> If I start manually with systemd-nspawn -M name -b, I seem to correctly
> get a new network namespace (ip link output in container is correct), but
> ls /sys
