Mailinglist Archive: opensuse-factory (437 mails)

< Previous Next >
Re: [opensuse-factory] Apparmor fails to start on boot in Tumbleweed
Hello,

Am Sonntag, 12. April 2015 schrieb Cristian Rodríguez:
On Sun, Apr 12, 2015 at 7:55 PM, Christian Boltz wrote:
How can I fix this?
- I'd love to simply add

ExecRestart=/etc/apparmor.d/boot.apparmor reload

Ooops.. I made a thinko.. it is ExecReload= that will do what you
want.

I'm afraid you mis-understood my mail :-(

The apparmor.service you sent with your SR contains ExecReload=, and
that works without problems.

The problem is that "systemctl restart" and "systemctl try-restart" mean
"stop, then start" - and that's a problem for AppArmor.
(BTW: The boot.apparmor initscript maps restart and try-restart to
reload. I need the same for systemd.)

Exactly for that reason I'm asking for a way to override the behaviour
of "restart". ExecRestart= would be an easy solution, but it's not
(yet?) a valid option in service files.

Feel free to consider this mail as feature request to implement
ExecRestart= in systemd ;-)

If there's a way to forbid usage of "restart" and "try-restart" (so that
only "reload" is permitted), I'd accept it as workaround. Displaying an
error message is still better than the current restart behaviour.


Regards,

Christian Boltz
--
which camera is this?
Marcus, this is my bug :)
[Marcus Meissner and Stephan Kulow in
https://bugzilla.novell.com/show_bug.cgi?id=217731]

--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
List Navigation
Follow Ups