202
edits
Changes
Updated OS X and Linux violation logging details
== Activity Logging ==
The following prefs control sandbox logging. On Windows, output is sent to the Browser Console when available, and to a developer console attached to the running browser process. On OSX, once enabled, violation log entries are visible in the Console.app (/Applications/Utilities/Console.app). On Linux, once enabled, violation log entries are logged on the command line console.<br/>
security.sandbox.logging.enabled (boolean)<br/>
MOZ_SANDBOX_LOGGING=1
=== OSX Specific Sandbox Logging ===
On Mac, sandbox violation logging is disabled by default. To enable logging,
* As of build 56, where filesystem read access restrictions were tightened, running Firefox always triggers sandbox violations and these will be logged. For example, plugin-container attempts to access /Applications and /Users (bug 1378968). We want to address these when possible, but some violations are complicated to avoid or are triggered by OS X library code that can't be avoided yet.
=== Linux specific Sandbox Logging ===
The following environment variable triggers extra sandbox debugging output: <br/>
