On Tue, Jan 17, 2017 at 10:15:11PM +0100, Christian Boltz wrote:
> argh, s/aa-mergeprof/aa-genprof/ here
> You are right. aa-mergeprof doesn't read the log and only takes another
> profile as input. I just noticed the bug in my question ;-)
Ah, good :)
> > In both cases, prompting the user seem
Hello,
Am Dienstag, 17. Januar 2017, 12:58:03 CET schrieb Seth Arnold:
> On Sun, Jan 15, 2017 at 04:24:46PM +0100, Christian Boltz wrote:
> > Everything below "if aamode == 'merge':" is an exact copy of the
> > code in aa-mergeprof (with whitespace changed).
> >
> > aa-logprof and aa-mergeprof wi
On Sun, Jan 15, 2017 at 04:24:46PM +0100, Christian Boltz wrote:
> Hello,
>
> $subject.
>
> Everything below "if aamode == 'merge':" is an exact copy of the code in
> aa-mergeprof (with whitespace changed).
>
> aa-logprof and aa-mergeprof will continue to ignore events from unknown
> hats and su
Hello,
$subject.
Everything below "if aamode == 'merge':" is an exact copy of the code in
aa-mergeprof (with whitespace changed).
aa-logprof and aa-mergeprof will continue to ignore events from unknown
hats and subprofiles.
RFC: does this make sense, or should aa-logprof and aa-mergeprof also
a
