diff options
| author | picca <picca@web> | 2015-10-02 08:48:46 +0000 |
|---|---|---|
| committer | admin <admin@branchable.com> | 2015-10-02 08:48:46 +0000 |
| commit | 4c464ef60e2980bb320513c124e934936da1707f (patch) | |
| tree | 84d2ea7b76e0f25d195faf1e0f2ef80bf61fe4cf | |
| parent | c619a661fb444ef892d336cd6a9ad953af898b49 (diff) | |
| -rw-r--r-- | doc/forum/PROPELLOR__95__DEBUG_doesn_not_propagate_to_the_host.mdwn | 9 |
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... |
