Implement skeletal ProcessSingleton on Linux to cut down on NOTIMPLEMENTED()s.

We now will refuse to run a second browser process if one is already running;
making the second invocation bring up new windows in the first remains left to
be implemented.

Review URL: http://codereview.chromium.org/20448


git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9980 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 3 insertions, 4 deletions

diff --git a/chrome/common/temp_scaffolding_stubs.h b/chrome/common/temp_scaffolding_stubs.h
index 3c7f710..2e487ac 100644
--- a/chrome/common/temp_scaffolding_stubs.h
+++ b/chrome/common/temp_scaffolding_stubs.h
@@ -109,10 +109,8 @@ class X509Certificate;
 //---------------------------------------------------------------------------
 // These stubs are for Browser_main()
 
-// TODO(port): the current ProcessSingleton implementation is very
-// windows-specific, but provides the concept of a singleton browser
-// process per user-data-dir. Investigate how achieve this on other
-// platforms and see if this API works.
+#if defined(OS_MACOSX)
+// TODO(port): needs an implementation of ProcessSingleton.
 class ProcessSingleton {
  public:
   explicit ProcessSingleton(const FilePath& user_data_dir) { }
@@ -126,6 +124,7 @@ class ProcessSingleton {
   void Lock() { NOTIMPLEMENTED(); }
   void Unlock() { NOTIMPLEMENTED(); }
 };
+#endif  // defined(OS_MACOSX)
 
 class GoogleUpdateSettings {
  public: