diff options
| author | suzhe@chromium.org <suzhe@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-07-31 05:31:27 +0000 |
|---|---|---|
| committer | suzhe@chromium.org <suzhe@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-07-31 05:31:27 +0000 |
| commit | dc609a177259742a89359fbb317d58b622af2f3f (patch) | |
| tree | 53f0715fece8e5e13e33f07e8b69d4c20202d756 /chrome/browser/sandbox_policy.cc | |
| parent | 731acac768c212b02df98e79f3355250c28e9253 (diff) | |
| download | chromium_src-dc609a177259742a89359fbb317d58b622af2f3f.zip chromium_src-dc609a177259742a89359fbb317d58b622af2f3f.tar.gz chromium_src-dc609a177259742a89359fbb317d58b622af2f3f.tar.bz2 | |
It's a copy of http://codereview.chromium.org/155772, with the fix for valgrind test failure.
This CL implements the second TODO item of issue 12343:
2) We should send back an ACK to the second process. If the second process doesn't get an ACK in the given timeout, it should kill the first process and go ahead and start.
The approach of this CL is to append process id to the singleton's socket filename, such as "SingletonSocket-12345", and creates a symbol link "SingletonSocket" to the real socket file. In ProcessSingleton::NotifyOtherProcess() if it's successfully connected to "SingletonSocket" but no ACK received, then the original process can be killed by its process id retrieved from the symbol link.
BUG=http://crbug.com/12343 ProcessSingleton Linux cleanups
TEST=In one terminal, launch chrome and stop the process by pressing ctrl-z, then launch chrome again in another terminal. The second chrome shall be started in 5 seconds, and the first one shall be killed.
Review URL: http://codereview.chromium.org/160436
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22144 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/sandbox_policy.cc')
0 files changed, 0 insertions, 0 deletions