diff options
author | rmsousa@chromium.org <rmsousa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-12 17:10:46 +0000 |
---|---|---|
committer | rmsousa@chromium.org <rmsousa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-12 17:10:46 +0000 |
commit | 8426f3aaa2ba2fe446512c4dbcd7bcf3b4c7eb4a (patch) | |
tree | ce95ef7caeffa717d76574cbd0eb9ba84109c25f /cc | |
parent | f94e0a0bc0bf8d3f55422deb0455d7e7a36cf364 (diff) | |
download | chromium_src-8426f3aaa2ba2fe446512c4dbcd7bcf3b4c7eb4a.zip chromium_src-8426f3aaa2ba2fe446512c4dbcd7bcf3b4c7eb4a.tar.gz chromium_src-8426f3aaa2ba2fe446512c4dbcd7bcf3b4c7eb4a.tar.bz2 |
Add notification when the host successfully starts.
This adds a listener for when first heartbeat is successful, which I think is the best signal that everything is working and the host is able to receive connections.
On Linux, that can send a signal if requested by the caller. On the script side, when running as a daemon, we create a pipe that allows the parent process to wait for that signal (or a permanent failure), and dump all Python log input to the STDERR. This gives users a much better feedback about whether starting the host worked or not.
BUG=179419
Review URL: https://chromiumcodereview.appspot.com/16448005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205837 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc')
0 files changed, 0 insertions, 0 deletions