I'm all up to move it to more appropriate config, even to separate config, rather than override, this was just place where I was testing it, to make sure time is adjusted before we start validating custom apparmor caches. I did not managed to get working TIME_ROOTFS formula in one go, that's the reason for double assignment. I attached modified config without double assignment.
On Fri, Nov 14, 2014 at 8:24 PM, Jamie Strandboge <ja...@ubuntu.com> wrote: > Assigning to package that ships /etc/init/custom-apparmor-cache.conf. > I'm not the owner of ubuntu-touch-customization-hooks so someone else > needs to land it. That said, the approach seems reasonable and the > script fine (though the double assignment for TIME_ROOTFS is not as > clear as it could be). However, I question whether this should be a pre- > start of custom-apparmor-cache.conf. On the one hand, we shouldn't need > this at all but because we do for custom-apparmor-cache to work right so > it makes sense, but on the other, perhaps this would be better placed in > a more 'foundational/phondational' package. Can we get someone from > Phonedations/Foundations to review and comment? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1385382 > > Title: > Clock set to past confuses AppArmor cache validation > > Status in AppArmor Linux application security framework: > Won't Fix > Status in “ubuntu-touch-customization-hooks” package in Ubuntu: > Triaged > > Bug description: > During initial boot sometimes clock could be set to past, which will > confuse logic validating precompiled AppArmour cache, causing cache > recreation. > If time is not set correct(valid) value, even consequent boots will fail > to validate cache, forcing cache recreation. > > This bug affects Initial out of the box experience, since device clock > is set in the factory to default value, for example 0:0am 1st of > January 2014 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/apparmor/+bug/1385382/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch- customization-hooks in Ubuntu. https://bugs.launchpad.net/bugs/1385382 Title: Clock set to past confuses AppArmor cache validation Status in AppArmor Linux application security framework: Won't Fix Status in “ubuntu-touch-customization-hooks” package in Ubuntu: Triaged Bug description: During initial boot sometimes clock could be set to past, which will confuse logic validating precompiled AppArmour cache, causing cache recreation. If time is not set correct(valid) value, even consequent boots will fail to validate cache, forcing cache recreation. This bug affects Initial out of the box experience, since device clock is set in the factory to default value, for example 0:0am 1st of January 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1385382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
