summaryrefslogtreecommitdiffstats
path: root/remoting/host/logging_win.cc
Commit message (Collapse)AuthorAgeFilesLines
* Only use the LoggingLock when actually logging to a fileakalin@chromium.org2013-07-151-3/+0
| | | | | | | | | | | Also coalesce some duplicated log-file-closing code. BUG=257196 R=alexeypa@chromium.org, darin@chromium.org Review URL: https://codereview.chromium.org/19091004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211709 0039d316-1c4b-4281-b951-d872f2087c98
* Do not use the logging lock since the debug log file is not used anyway.alexeypa@chromium.org2013-07-111-0/+3
| | | | | | | | BUG=257196 Review URL: https://chromiumcodereview.appspot.com/18210006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211205 0039d316-1c4b-4281-b951-d872f2087c98
* Define a LoggingSettings struct to use for InitLogging()akalin@chromium.org2013-06-211-6/+3
| | | | | | | | | | | | | | | | | | Update all callers of InitLogging() to use LoggingSettings, only setting fields that need a non-default value. Turn LoggingDestination enum into a bit field and define add LOG_DEFAULT and LOG_ALL constants. Fix erroneous comment saying that the default was to not lock the log file. BUG=247594 TBR=brettw@chromium.org, cpu@chromium.org, gene@chromium.org, jam@chromium.org, rch@chromium.org, scherkus@chromium.org, sergeyu@chromium.org, sky@chromium.org, tkent@chromium.org, yfriedman@chromium.org, zea@chromium.org Review URL: https://codereview.chromium.org/16519003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207920 0039d316-1c4b-4281-b951-d872f2087c98
* Stop writing logs to %ProgramData%\Chromoting\debug.log (Windows only).alexeypa@chromium.org2013-01-081-16/+2
| | | | | | | | | | | %ProgramData% is read-only for processes running at low integrity level. since the host is now running at low integrity level and logs are written to ETW, this CL quits using debug.log altogether. See http://code.google.com/p/sawbuck/wiki/HowToCaptureLogsOffline for an example how logs can be collected via ETW infrastructure. The Chromoting provider's guid is "{2db51ca1-4fd8-4b88-b5a2-fb8606b66b02}". BUG=134694 Review URL: https://chromiumcodereview.appspot.com/11776029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@175433 0039d316-1c4b-4281-b951-d872f2087c98
* Redirect Chromoting Host debug logs to Windows event tracing (ETW) instead ↵alexeypa@chromium.org2012-10-181-0/+46
of a file on disk. This CL prevents infinite growth of debug.log over time. The debug output is redirected to ETW logging. Sawbuck (http://code.google.com/p/sawbuck/) or standard ETW tools can be used to view the debug output. The debug build still uses "debug.log" (along with ETW) to simplify debugging. The installation registers "Chromoting" provider with Sawbuck and deletes the existing "debug.log" file during both installation and uninstallation. BUG=156135 Review URL: https://chromiumcodereview.appspot.com/11188016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162614 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-16 00:49:27 +0000