[apparmor] [patch] Add realtime signal example to the apparmor.d manpage
Christian Boltz
apparmor at cboltz.de
Wed Dec 2 19:52:20 UTC 2015
Hello,
Am Dienstag, 24. November 2015 schrieb Steve Beattie:
> On Tue, Nov 24, 2015 at 11:04:14PM +0100, Christian Boltz wrote:
> > I propose this patch for trunk, 2.10 and 2.9 (assuming real-time
> > signals were supported in those versions).
>
> Acked-by: Steve Beattie <steve at nxnw.org> for all 3.
>
> It would also be good to add them into the pseudo-BNF description of
> the language earlier in the same man page.
Good idea, here's the follow-up patch for it.
(I'm not sure if the syntax I used is exactly what we want - if you
think we should use another syntax to specify a range, please tell me.)
[patch] Add realtime signals to SIGNALS list in apparmor.d
I propose this patch for trunk, 2.10 and 2.9.
[ apparmor.d-add-rtmin-to-signal-list.diff ]
=== modified file 'parser/apparmor.d.pod'
--- parser/apparmor.d.pod 2015-08-25 11:27:18 +0000
+++ parser/apparmor.d.pod 2015-12-02 19:13:22 +0000
@@ -161,7 +161,7 @@
B<SIGNAL LIST> = Comma or space separated list of I<SIGNALS>
-B<SIGNALS> = ( 'hup' | 'int' | 'quit' | 'ill' | 'trap' | 'abrt' | 'bus' | 'fpe' | 'kill' | 'usr1' | 'segv' | 'usr2' | 'pipe' | 'alrm' | 'term' | 'stkflt' | 'chld' | 'cont' | 'stop' | 'stp' | 'ttin' | 'ttou' | 'urg' | 'xcpu' | 'xfsz' | 'vtalrm' | 'prof' | 'winch' | 'io' | 'pwr' | 'sys' | 'emt' | 'exists' )
+B<SIGNALS> = ( 'hup' | 'int' | 'quit' | 'ill' | 'trap' | 'abrt' | 'bus' | 'fpe' | 'kill' | 'usr1' | 'segv' | 'usr2' | 'pipe' | 'alrm' | 'term' | 'stkflt' | 'chld' | 'cont' | 'stop' | 'stp' | 'ttin' | 'ttou' | 'urg' | 'xcpu' | 'xfsz' | 'vtalrm' | 'prof' | 'winch' | 'io' | 'pwr' | 'sys' | 'emt' | 'exists' | 'rtmin+0' ... 'rtmin+32' )
B<SIGNAL PEER> = 'peer' '=' I<AARE>
Regards,
Christian Boltz
--
no, trolling on a mailing list is not a contribution.. If 1% of
the time spent on trolling on Factory mailing list was spent on
fixing bugs or developing features, we would be number 1..
[Frederic Crozat on opensuse-factory]
More information about the AppArmor
mailing list