diff options
| author | jorgelo@chromium.org <jorgelo@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-07-12 20:23:28 +0000 |
|---|---|---|
| committer | jorgelo@chromium.org <jorgelo@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-07-12 20:23:28 +0000 |
| commit | 028ad790af8a56daf64aeebb49dcbb7c296ac645 (patch) | |
| tree | e25fc4874204626e0f0b714e5309bf8e62d8029a /content/content_shell.gypi | |
| parent | 028211009a34c8cb7d9883fc4b333dc9847c51b6 (diff) | |
| download | chromium_src-028ad790af8a56daf64aeebb49dcbb7c296ac645.zip chromium_src-028ad790af8a56daf64aeebb49dcbb7c296ac645.tar.gz chromium_src-028ad790af8a56daf64aeebb49dcbb7c296ac645.tar.bz2 | |
Disable seccomp filter sandbox temporarily.
We have one report of weird behaviour with seccomp filter and
3.5 kernels.
Keep a workaround by defining a "CHROME_ENABLE_SECCOMP" env var.
BUG=None
TEST=No "Activated seccomp filter sandbox for process type..." messages in log.
Review URL: https://chromiumcodereview.appspot.com/10703170
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146434 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/content_shell.gypi')
0 files changed, 0 insertions, 0 deletions