From 7839cee20f8fe5742ba5f0750aae071a0b68fba9 Mon Sep 17 00:00:00 2001
From: rillig <rillig>
Date: Thu, 9 Nov 2006 02:11:44 +0000
Subject: In the status and error messages, say _which_ lock is being held by
 another process. It's a little more verbose now, but it helps understanding
 what goes on.

---
 mk/internal/locking.mk | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'mk/internal')

diff --git a/mk/internal/locking.mk b/mk/internal/locking.mk
index 4943835212e..cda52892bdf 100644
--- a/mk/internal/locking.mk
+++ b/mk/internal/locking.mk
@@ -1,4 +1,4 @@
-# $NetBSD: locking.mk,v 1.2 2006/08/04 20:52:27 rillig Exp $
+# $NetBSD: locking.mk,v 1.3 2006/11/09 02:11:44 rillig Exp $
 #
 
 # This file provides the following .USE targets:
@@ -77,10 +77,10 @@ _ACQUIRE_LOCK_CMD= \
 		fi;							\
 		lockpid=`${CAT} "$$lockfile"`;				\
 		case ${PKGSRC_LOCKTYPE:Q}"" in				\
-		once)	${ERROR_MSG} "Lock is held by pid $$lockpid";	\
+		once)	${ERROR_MSG} "Lock ${.TARGET} is held by pid $$lockpid";	\
 			exit 1;						\
 			;;						\
-		sleep)	${STEP_MSG} "Lock is held by pid $$lockpid";	\
+		sleep)	${STEP_MSG} "Lock ${.TARGET} is held by pid $$lockpid";	\
 			${SLEEP} ${PKGSRC_SLEEPSECS};			\
 			;;						\
 		esac;							\
-- 
cgit v1.2.3