summaryrefslogtreecommitdiff
path: root/doc/forum/PROPELLOR__95__DEBUG_doesn_not_propagate_to_the_host.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/PROPELLOR__95__DEBUG_doesn_not_propagate_to_the_host.mdwn')
-rw-r--r--doc/forum/PROPELLOR__95__DEBUG_doesn_not_propagate_to_the_host.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/forum/PROPELLOR__95__DEBUG_doesn_not_propagate_to_the_host.mdwn b/doc/forum/PROPELLOR__95__DEBUG_doesn_not_propagate_to_the_host.mdwn
new file mode 100644
index 00000000..aa0e2537
--- /dev/null
+++ b/doc/forum/PROPELLOR__95__DEBUG_doesn_not_propagate_to_the_host.mdwn
@@ -0,0 +1,9 @@
+While investigating my rm property problem I ran propellor with
+
+ PROPELLOR_DEBUG=1 propellor
+
+At the beginning I have the debug informations but not once the ssh connection was initiated on the host.
+
+So I had to log into the host in order to run locally propellor in debug mode.
+
+It seems to me that the PROPELLOR_DEBUG=1 env should be propagate to the host, chroot etc...