On Mon, 23.05.16 22:45, Christian Boltz (systemd-de...@cboltz.de) wrote:
> > We don't support that as our logic permits merging of jobs. This means
> > that if two clients enqueue two stop or two start jobs at the same
> > time, then we will only actually run one. In fact, this merging of
> > jobs
On Mon, 23.05.16 22:52, Christian Boltz (systemd-de...@cboltz.de) wrote:
> > It appears to me, that you are trying to map something onto the
> > "service" concept, that probably shouldn't really be a service. As
> > someone who really doesn't know aa I'd probably suggest to have some
> > tool mayb
Am 23.05.2016 um 23:33 schrieb Michael Biebl:
2016-05-23 22:52 GMT+02:00 Christian Boltz :
I'd argue that nobody will complain if "systemctl restart apparmor" does
something sane (reloading the profiles) instead of making the system
insecure by removing the confinement from all running process
2016-05-23 22:52 GMT+02:00 Christian Boltz :
> I'd argue that nobody will complain if "systemctl restart apparmor" does
> something sane (reloading the profiles) instead of making the system
> insecure by removing the confinement from all running processes ;-)
So, you really want reload here, not
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
> > from the kernel. The result is that all A
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
> >
> > systemctl stop foo; systemctl start foo
> >
> > Unfortunately
On Mon, 23.05.16 13:11, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> On Mon, May 23, 2016 at 12:25 PM, Lennart Poettering
> wrote:
> > On Sat, 21.05.16 10:31, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> >
> >> >> I need a way to know if "restart "or "stop" was used because the mapping
> >>
On Mon, May 23, 2016 at 12:25 PM, Lennart Poettering
wrote:
> On Sat, 21.05.16 10:31, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
>> >> I need a way to know if "restart "or "stop" was used because the mapping
>> >> to stop / start gives my service a completely different behaviour than
>> >> ex
On Sun, 22.05.16 23:19, Christian Boltz (systemd-de...@cboltz.de) wrote:
> 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 user
On Sun, 22.05.16 16:18, Christian Boltz (systemd-de...@cboltz.de) wrote:
> I can add my usecase as another reason ;-)
>
> I'm talking about AppArmor, where "stop" means unloading the profiles
> from the kernel. The result is that all AppArmor confinement is removed
> from all running processes.
On Sat, 21.05.16 10:31, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> >> I need a way to know if "restart "or "stop" was used because the mapping
> >> to stop / start gives my service a completely different behaviour than
> >> expected on restart.
> >>
> >> Is there a way to find out if "stop" o
On Fri, 20.05.16 21:50, Christian Boltz (systemd-de...@cboltz.de) wrote:
> Hello,
>
> it looks like
> systemctl restart foo
> is internally mapped to a sequence of
> systemctl stop foo; systemctl start foo
>
> Unfortunately, this behaviour causes quite some trouble for me.
>
> I need a
Hi,
Internally systemd, does differentiate between
stop - start
and
restart
because when you use restart, it preserves any FDs that were saved across
the stop and provides it to the start, but does not do the same thing, when
the user explictly does a stop/start.
I think it would be nice
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
> > (and avoid restart).
> >
> > Ple
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 (and avoid
restart).
Please read the paragraph above the ^^^ marker again.
The problem is what happens when someo
On Sun, May 22, 2016 at 10:03 PM, Christian Boltz
wrote:
> 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.
> > >
> > > Thi
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_ processes won't be
> > (re)confined [
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_ processes won't be (re)confined [1],
> which translates a small typo done by the admin ("systemctl restart
> appa
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
> >>
> >> systemctl stop foo; systemctl start f
21.05.2016 05:59, Reindl Harald пишет:
>
>
> Am 20.05.2016 um 21:50 schrieb Christian Boltz:
>> Hello,
>>
>> it looks like
>> systemctl restart foo
>> is internally mapped to a sequence of
>> systemctl stop foo; systemctl start foo
>
> what else?
>
>> Unfortunately, this behaviour cause
Am 20.05.2016 um 21:50 schrieb Christian Boltz:
Hello,
it looks like
systemctl restart foo
is internally mapped to a sequence of
systemctl stop foo; systemctl start foo
what else?
Unfortunately, this behaviour causes quite some trouble for me.
why?
I need a way to know if "rest
Hello,
it looks like
systemctl restart foo
is internally mapped to a sequence of
systemctl stop foo; systemctl start foo
Unfortunately, this behaviour causes quite some trouble for me.
I need a way to know if "restart "or "stop" was used because the mapping
to stop / start gives my serv
22 matches
Mail list logo
