You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by to...@apache.org on 2019/12/21 11:45:45 UTC
[libcloud] 05/09: Add a note on paramiko logger opening log file in
append mode which won't work in all the distros.
This is an automated email from the ASF dual-hosted git repository.
tomaz pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/libcloud.git
commit b5ebd83476ba515c237118242d2823f9b3e9ba6b
Author: Tomaz Muraus <to...@tomaz.me>
AuthorDate: Sat Dec 21 12:27:08 2019 +0100
Add a note on paramiko logger opening log file in append mode which
won't work in all the distros.
---
docs/troubleshooting.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/docs/troubleshooting.rst b/docs/troubleshooting.rst
index 8c12103..f4b299a 100644
--- a/docs/troubleshooting.rst
+++ b/docs/troubleshooting.rst
@@ -41,6 +41,15 @@ only works for non-chunked responses.
Example 1 - Logging output to standard error
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.. note::
+
+ Some Linux distributions don't allow /dev/{stderr,stdout} to be opened in
+ append mode which means paramiko logger will return and error that it
+ can't log to that file.
+ In such scenario, it's recommended you specify actual file path and then
+ you can use "tail -F" in another terminal window to view the output in
+ real-time.
+
If you want the output to be logged to the standard error (on
Linux) you can set it to ``/dev/stderr``: