No, the problem, was that setting CHROMIUM_FLAGS disk-cache-size to 0 does not limit the cache to 0, instead it uses the default. Setting it to 10M works, and even better as a policy than as a flag. So I think the bug is invalid as chromium behaves as documented (if not entirely as expected).
On 17 December 2013 16:44, Chad Miller <chad.mil...@canonical.com> wrote: > Is CHROMIUM_USER_FLAGS set in any environment? Those take precedence > over CHROMIUM_FLAGS . > > ** Changed in: chromium-browser (Ubuntu) > Status: Invalid => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1259933 > > Title: > chromium-browser ignores CHROMIUM_FLAGS > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1259933/+subscriptions > -- .~. /V\ Jan Groenewald /( )\ www.aims.ac.za ^^-^^ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259933 Title: chromium-browser ignores CHROMIUM_FLAGS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1259933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
