Fix DBus client binding to Manager interface of peerd.

Fix DBus client binding to Manager interface of peerd.

Consumers of this API would crash since Init wasn't getting called.
Also the incorrect dbus object was getting called.

BUG=441765
Committed: https://crrev.com/e8c3bb6ff1cc00179a4ba3b4e0f348418342b1f5
Cr-Commit-Position: refs/heads/master@{#311779}

[dtapuska, 2015-01-14 15:21:32]

dtapuska@chromium.org changed reviewers:
+ benchan@chromium.org, pwestin@chromium.org, stevenjb@chromium.org,
wiley@chromium.org

[stevenjb, 2015-01-14 16:30:01]

stevenjb@chromium.org changed required reviewers:
+ benchan@chromium.org

[stevenjb, 2015-01-14 16:30:02]

owner lgtm

[pwestin(chromium), 2015-01-14 16:44:02]

lgtm

[wiley, 2015-01-14 18:20:04]

https://codereview.chromium.org/847313003/diff/1/chromeos/dbus/peer_daemon_ma...
File chromeos/dbus/peer_daemon_manager_client.cc (right):

https://codereview.chromium.org/847313003/diff/1/chromeos/dbus/peer_daemon_ma...
chromeos/dbus/peer_daemon_manager_client.cc:22: const char kPeerdServicePath[] =
"/org/chromium/peerd/Manager";
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:02:33]

The CQ bit was checked by dtapuska@chromium.org

[dtapuska, 2015-01-14 19:02:41]

The CQ bit was unchecked by dtapuska@chromium.org

[dtapuska, 2015-01-14 19:03:51]

The CQ bit was checked by dtapuska@chromium.org

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

https://codereview.chromium.org/847313003/diff/1/chromeos/dbus/peer_daemon_ma...
File chromeos/dbus/peer_daemon_manager_client.cc (right):

https://codereview.chromium.org/847313003/diff/1/chromeos/dbus/peer_daemon_ma...
chromeos/dbus/peer_daemon_manager_client.cc:22: const char kPeerdServicePath[] =
"/org/chromium/peerd/Manager";
On 2015/01/14 18:20:03, wiley wrote:
> 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.

Done.

[commit-bot: I haz the power, 2015-01-14 19:05:56]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/847313003/20001

[commit-bot: I haz the power, 2015-01-14 19:05:58]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-14 19:05:59]

All required reviewers (with asterisk prefixes) have not yet approved this CL.

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[wiley, 2015-01-14 20:40:44]

Thanks!  LGTM

[Ben Chan, 2015-01-15 20:36:54]

lgtm

[dtapuska, 2015-01-15 21:27:00]

The CQ bit was checked by dtapuska@chromium.org

[commit-bot: I haz the power, 2015-01-15 21:28:39]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/847313003/20001

[commit-bot: I haz the power, 2015-01-16 00:35:50]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-01-16 00:37:11]

Patchset 2 (id:??) landed as
https://crrev.com/e8c3bb6ff1cc00179a4ba3b4e0f348418342b1f5
Cr-Commit-Position: refs/heads/master@{#311779}