[Chromoting] Hook up host talkgadget policy checks.

remoting/host/policy_hack/policy_watcher_linux.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Most of this code is copied from various classes in
 // src/chrome/browser/policy. In particular, look at
 //
 //   file_based_policy_loader.{h,cc}
 //   config_dir_policy_provider.{h,cc}
 //
@@ skipping 15 matching lines @@
 #include "base/synchronization/waitable_event.h"
 #include "base/time.h"
 #include "base/values.h"
 
 namespace remoting {
 namespace policy_hack {
 
 namespace {
 
 const FilePath::CharType kPolicyDir[] =
+#if defined(OFFICIAL_BUILD)
     FILE_PATH_LITERAL("/etc/opt/chrome/policies/managed");
+#else
+    FILE_PATH_LITERAL("/etc/chromium/policies/managed");

[Sergey Ulanov, 2012/08/24 19:43:33]

Was it intentional change?
We always want to look at the Chrome's policies, even in chromium builds.
Otherwise it would be really easy to workaround chrome policies by running
chromium build. That's also the way Mac and Windows policy watchers work.

[garykac, 2012/08/27 22:34:57]

Ah. I didn't realize that (and it's easier to edit my chromium settings). I've
added a comment.

+#endif
 
 // Amount of time we wait for the files on disk to settle before trying to load
 // them. This alleviates the problem of reading partially written files and
 // makes it possible to batch quasi-simultaneous changes.
 const int kSettleIntervalSeconds = 5;
 
 }  // namespace
 
 class PolicyWatcherLinux : public PolicyWatcher {
  public:
@@ skipping 222 matching lines @@
 };
 
 PolicyWatcher* PolicyWatcher::Create(
     scoped_refptr<base::SingleThreadTaskRunner> task_runner) {
   FilePath policy_dir(kPolicyDir);
   return new PolicyWatcherLinux(task_runner, policy_dir);
 }
 
 }  // namespace policy_hack
 }  // namespace remoting