Michael S. Fischer 43ab372a18 lock.go: fix another race condition
The previous fix to `consul lock` (commit 6875e8d) didn't completely
eliminate the race that could occur if the lock was acquired around the
same time SIGTERM was received:  It was still possible for
Run() to spawn the process via startChild() after killChild() had
released the shared mutex.

Now, when SIGTERM is received, we acquire a mutex that prevents
spawning a new process and never release it.

We've tested this fix pretty thoroughly and believe it completely
resolves the issue.
2015-09-01 14:27:23 -07:00
..
2015-05-08 13:09:50 -07:00
2015-01-19 15:47:17 -10:00
2015-09-01 14:27:23 -07:00
2014-06-11 10:58:26 -07:00
2015-01-25 05:00:52 +01:00
2014-08-21 16:08:21 -07:00