Re: [apparmor] [PATCH 01/31] change cache check so that debugging can see which file caused failure

2014-12-11 Thread Christian Boltz
Hello, Am Mittwoch, 10. Dezember 2014 schrieb Tyler Hicks: > Modifying the way that cache files are creating, by setting their > timestamp, is outside of the scope of this patch set. I think it is a > good feature to implement but it is not something that I'm willing to > entertain in this set of

Re: [apparmor] [PATCH 01/31] change cache check so that debugging can see which file caused failure

2014-12-10 Thread Tyler Hicks
On 2014-12-06 15:05:51, Christian Boltz wrote: > Hello, > > Am Freitag, 5. Dezember 2014 schrieb Tyler Hicks: > > Currently the cache tracks the most recent timestamp of parsed files > > and then compares that to the cache timestamp. This unfortunately > > prevents the parser from being able to kn

Re: [apparmor] [PATCH 01/31] change cache check so that debugging can see which file caused failure

2014-12-06 Thread Christian Boltz
Hello, Am Freitag, 5. Dezember 2014 schrieb Tyler Hicks: > Currently the cache tracks the most recent timestamp of parsed files > and then compares that to the cache timestamp. This unfortunately > prevents the parser from being able to know which files caused the > cache check failure. > > Rewor

[apparmor] [PATCH 01/31] change cache check so that debugging can see which file caused failure

2014-12-05 Thread Tyler Hicks
From: John Johansen Currently the cache tracks the most recent timestamp of parsed files and then compares that to the cache timestamp. This unfortunately prevents the parser from being able to know which files caused the cache check failure. Rework the cache check so that there is a debug optio