diff options
| author | evan@chromium.org <evan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-12-15 00:44:03 +0000 |
|---|---|---|
| committer | evan@chromium.org <evan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-12-15 00:44:03 +0000 |
| commit | 7975d395a2ee0d8b5ba8aa4748c950e9e957503d (patch) | |
| tree | 4ec92d863c274739331d888e639afc92305b2cfa /chrome/browser/zygote_host_linux.cc | |
| parent | f52832291a312d78592aac0744809ed02822bfa9 (diff) | |
| download | chromium_src-7975d395a2ee0d8b5ba8aa4748c950e9e957503d.zip chromium_src-7975d395a2ee0d8b5ba8aa4748c950e9e957503d.tar.gz chromium_src-7975d395a2ee0d8b5ba8aa4748c950e9e957503d.tar.bz2 | |
seccomp: remove build-time flags
Adjusting seccomp through the .gyp file is error-prone and confusing.
Instead, because all callers call SeccompSandboxEnabled(), if I
want to enable it for some build configuration I can adjust just that
function.
This change removes all the build-time seccomp configuration and
leaves it defaulted off. It should have no change on whether seccomp
is enabled.
Review URL: http://codereview.chromium.org/5844001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69208 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/zygote_host_linux.cc')
| -rw-r--r-- | chrome/browser/zygote_host_linux.cc | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/chrome/browser/zygote_host_linux.cc b/chrome/browser/zygote_host_linux.cc index e4e7ce3..a908e86 100644 --- a/chrome/browser/zygote_host_linux.cc +++ b/chrome/browser/zygote_host_linux.cc @@ -104,11 +104,8 @@ void ZygoteHost::Init(const std::string& sandbox_cmd) { switches::kUserDataDir, // Make logs go to the right file. // Load (in-process) Pepper plugins in-process in the zygote pre-sandbox. switches::kRegisterPepperPlugins, -#if defined(USE_SECCOMP_SANDBOX) switches::kDisableSeccompSandbox, -#else switches::kEnableSeccompSandbox, -#endif }; cmd_line.CopySwitchesFrom(browser_command_line, kForwardSwitches, arraysize(kForwardSwitches)); |