Hello,
Am Montag, 23. Mai 2016, 11:43:13 CEST schrieb Lennart Poettering:
> On Sun, 22.05.16 16:18, Christian Boltz wrote:
> > I can add my usecase as another reason ;-)
> >
> > I'm talking about AppArmor, where "stop" means unloading the
> > profiles
&
Hello,
Am Montag, 23. Mai 2016, 11:24:06 CEST schrieb Lennart Poettering:
> On Fri, 20.05.16 21:50, Christian Boltz wrote:
> > it looks like
> >
> > systemctl restart foo
> >
> > is internally mapped to a sequence of
> >
> >
Hello,
Am Sonntag, 22. Mai 2016, 21:48:02 CEST schrieb Reindl Harald:
> Am 22.05.2016 um 21:03 schrieb Christian Boltz:
> > I'm already using ExecReload= to reload the profiles (works fine),
> > and hope all users actually read the documentation and use reload
&g
Hello,
Am Sonntag, 22. Mai 2016, 20:24:53 CEST schrieb Martin Pitt:
> Christian Boltz [2016-05-22 16:18 +0200]:
> > "start" means loading the profiles and applying the confinement to
> > _newly started_ profiles.
> >
> > This also means that _already running
Hello,
Am Samstag, 21. Mai 2016, 10:31:22 CEST schrieb Andrei Borzenkov:
> 21.05.2016 05:59, Reindl Harald пишет:
> > Am 20.05.2016 um 21:50 schrieb Christian Boltz:
> >> systemctl restart foo
> >>
> >> is internally mapped to a sequence of
> >>
t. (Or did I overlook it? The manpagesare long and
detailed (thanks for that!), but that makes it easy to overlook something ;-)
Regards,
Christian Boltz
[1]
https://lists.freedesktop.org/archives/systemd-devel/2016-January/035577.html
--
what does "> /dev/null" mean?
and how do i
be somewhat random/racy because the
kill can happen at different states of the restart.
Can you still reproduce the issue you described if you at least add a
"sleep 5" before killing systemctl?
Regards,
Christian Boltz
--
[Greylisting ist] das alte Hotline-Prinzip: Wenn der 4 Minuten lang