From c3f7973c24b97f48b751cfd7194dbef26d35f511 Mon Sep 17 00:00:00 2001 From: Rohit Makasana Date: Mon, 12 Aug 2013 12:58:05 +0530 Subject: [PATCH] Adding a lock mechanism to crash_sender. This is to avoid situations when crash_sender is already running and while test crash reporting, we execute crash_sender manually. BUG=None TEST=Manually Change-Id: I3beea8d503940d7a1af24c8f16eebb365d447434 Reviewed-on: https://gerrit.chromium.org/gerrit/65556 Reviewed-by: Mike Frysinger Commit-Queue: Rohit Makasana Reviewed-by: Rohit Makasana Tested-by: Rohit Makasana --- crash_reporter/crash_sender | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/crash_reporter/crash_sender b/crash_reporter/crash_sender index 72205cffc..0422ca20f 100755 --- a/crash_reporter/crash_sender +++ b/crash_reporter/crash_sender @@ -18,6 +18,9 @@ CLEAN_UP_RUN_FILE=0 # contents includes our machine's anonymized guid. CONSENT_ID="/home/chronos/Consent To Send Stats" +# Crash sender lock in case the sender is already running. +CRASH_SENDER_LOCK="/var/lock/crash_sender" + # Path to file that indicates a crash test is currently running. CRASH_TEST_IN_PROGRESS_FILE="/tmp/crash-test-in-progress" @@ -569,4 +572,10 @@ main() { done } +( +if ! flock -n 9; then + lecho "crash_sender is already running; quitting." + exit 1 +fi main +) 9>"${CRASH_SENDER_LOCK}"