From 492064f8e2d1e53ffc1ac1b23099f85ffc13ab7d Mon Sep 17 00:00:00 2001
From: Orsiris de Jong <ozy@netpower.fr>
Date: Fri, 5 Jul 2019 22:24:48 +0200
Subject: [PATCH] Comment about _REMOTE_EXECUTION variable

---
 dev/ofunctions.sh | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/dev/ofunctions.sh b/dev/ofunctions.sh
index 339ba48..7edf492 100644
--- a/dev/ofunctions.sh
+++ b/dev/ofunctions.sh
@@ -116,6 +116,8 @@ else
 fi
 
 ## Special note when remote target is on the same host as initiator (happens for unit tests): we'll have to differentiate RUN_DIR so remote CleanUp won't affect initiator.
+## If the same program gets remotely executed, add _REMOTE_EXECUTION=true to it's environment so it knows it has to write into a separate directory
+## This will thus not affect local $RUN_DIR variables
 if [ "$_REMOTE_EXECUTION" == true ]; then
 	mkdir -p "$RUN_DIR/$PROGRAM.remote"
 	RUN_DIR="$RUN_DIR/$PROGRAM.remote"