Enable control of verbose logging via --v and --vmodule.

This just requires that we initialize logging with InitLogging() at startup.  It can be used to enable "verbose" logging to aid debugging, e.g.:

remoting_me2me_host --v=3


Review URL: http://codereview.chromium.org/10021038

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132752 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 6 insertions, 3 deletions

diff --git a/remoting/host/remoting_me2me_host.cc b/remoting/host/remoting_me2me_host.cc
index 8ed3f32..3812854 100644
--- a/remoting/host/remoting_me2me_host.cc
+++ b/remoting/host/remoting_me2me_host.cc
@@ -401,16 +401,19 @@ int main(int argc, char** argv) {
   // LazyInstance, MessageLoop).
   base::AtExitManager exit_manager;
 
-#if defined(OS_WIN)
-  // Write logs to the application profile directory.
+  // Initialize logging with an appropriate log-file location, and default to
+  // log to that on Windows, or to standard error output otherwise.
   FilePath debug_log = remoting::GetConfigDir().
       Append(FILE_PATH_LITERAL("debug.log"));
   InitLogging(debug_log.value().c_str(),
+#if defined(OS_WIN)
               logging::LOG_ONLY_TO_FILE,
+#else
+              logging::LOG_ONLY_TO_SYSTEM_DEBUG_LOG,
+#endif
               logging::DONT_LOCK_LOG_FILE,
               logging::APPEND_TO_OLD_LOG_FILE,
               logging::DISABLE_DCHECK_FOR_NON_OFFICIAL_RELEASE_BUILDS);
-#endif
 
   const CommandLine* cmd_line = CommandLine::ForCurrentProcess();