Log host startup (Linux/Mac)

remoting/host/host_event_logger_posix.cc

Index: remoting/host/host_event_logger_posix.cc
diff --git a/remoting/host/host_event_logger_posix.cc b/remoting/host/host_event_logger_posix.cc
index 33b4b311407d1f32268ba411256256d3a7e1196e..eb5361ec3df9bc31d79763bdb7ac0cb8b3648961 100644
--- a/remoting/host/host_event_logger_posix.cc
+++ b/remoting/host/host_event_logger_posix.cc
@@ -56,6 +56,7 @@ HostEventLoggerPosix::HostEventLoggerPosix(ChromotingHost* host,
       application_name_(application_name) {
   openlog(application_name_.c_str(), 0, LOG_USER);
   host_->AddStatusObserver(this);
+  Log("Host started");

[Jamie, 2012/07/18 23:21:34]

Please run this string by the relevant stakeholders to make sure it's specific
enough. Ideally, it should be possible to identify all of our log messages with
a single grep.

[Sergey Ulanov, 2012/07/18 23:28:17]

It's already possible to do that - syslog logs application name next to each
message. application name is specified in the openlog() call above.

[Lambros, 2012/07/18 23:40:56]

I think this string is sufficiently distinctive from the other strings logged
here.  If an objection is raised, we can always change it again :)

[Wez, 2012/07/19 00:41:29]

nit: I think this can simply be "Started" - we already know it's the host
logging it in both syslog and Windows' Event Log.

[Lambros, 2012/07/19 01:36:34]

OK.  If we ever need Host/Client distinction, that should go in the
application_name.

 }
 
 HostEventLoggerPosix::~HostEventLoggerPosix() {