Fix DBus client binding to Manager interface of peerd.

chromeos/dbus/peer_daemon_manager_client.cc

Index: chromeos/dbus/peer_daemon_manager_client.cc
diff --git a/chromeos/dbus/peer_daemon_manager_client.cc b/chromeos/dbus/peer_daemon_manager_client.cc
index 99a362a29c6158d40307408e0eb16a8049576e60..92f90a0c5a49955edfb09453b291f966b2902d4b 100644
--- a/chromeos/dbus/peer_daemon_manager_client.cc
+++ b/chromeos/dbus/peer_daemon_manager_client.cc
@@ -19,7 +19,7 @@ namespace {
 // TODO(benchan): Move these constants to system_api.
 namespace peerd {
 const char kPeerdServiceName[] = "org.chromium.peerd";
-const char kPeerdServicePath[] = "/org/chromium/peerd";
+const char kPeerdServicePath[] = "/org/chromium/peerd/Manager";

[wiley, 2015/01/14 18:20:03]

Calling this DBus path ServicePath is misleading.  This is the path of the
manager within peerd.  There is for instance an ObjectManager at
/org/chromium/peerd and a number of service objects, each with their own unique
service paths.

[dtapuska, 2015/01/14 19:04:34]

Done.

 const char kManagerInterface[] = "org.chromium.peerd.Manager";
 const char kStartMonitoringMethod[] = "StartMonitoring";
 const char kStopMonitoringMethod[] = "StopMonitoring";