I tried running in background, and sending SIGUSR1

That will get passed on to our program, and we'll
do a clean shutdown.  Unfortunately, it seems that the
leaks are from the first call to logging.

I can't seem to do anything about those leaks.

grind.sh

@@ -3,12 +3,13 @@
 # valgrind -v --log-file=grind.log build/space-ace -l -u grinder
 
 # start in background
-valgrind -v --leak-check=full --show-leak-kinds=all --log-file=grind.log build/twproxy grind.yaml &
+# valgrind -v --leak-check=full --show-leak-kinds=all --log-file=grind.log build/twproxy grind.yaml &
 
-PID=$!
-echo "valgrind is pid $PID"
-ps --ppid $PID
+# valslow:
+# valgrind -v --leak-check=full --track-origins=yes --leak-resolution=high --read-var-info=yes --read-inline-info=yes --show-leak-kinds=all --log-file=grind.log build/twproxy grind.yaml &
 
-wait
+# valgrind -v --leak-check=full --leak-resolution=high --show-leak-kinds=all --log-file=grind.log build/twproxy grind.yaml &
+
+valgrind -v --leak-check=full --leak-resolution=high --show-leak-kinds=all --log-file=grind.log build/twproxy grind.yaml 
 
 tail grind.log