From 22774aabca1c1470f36ed5dbcd49d90eec18fb32 Mon Sep 17 00:00:00 2001
From: Alfonso Acosta <alfonso.acosta@gmail.com>
Date: Fri, 29 Jan 2016 14:44:21 +0000
Subject: [PATCH] Update approach to trigger signal dumps

pkill's flags vary in different systems, plus it will just be silent if it doesn't match any process
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index e5ff4df24..511698d68 100644
--- a/README.md
+++ b/README.md
@@ -220,14 +220,14 @@ Scope has a collection of built in debugging tools to aid Scope delevopers.
 
 - To have the Scope App or Scope Probe dump their goroutine stacks, run:
 ```
-pkill -SIGQUIT scope-(app|probe)
+kill -QUIT $(pgrep -f scope-(app|probe))
 docker logs weavescope
 ```
 
 - The Scope Probe is instrumented with various counters and timers. To have it dump
   those values, run:
 ```
-pkill -SIGUSR1 scope-probe
+kill -USR1 $(pgrep -f scope-probe)
 docker logs weavescope
 ```