-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mkcloud needs to automatically log itself to a file #1191
Labels
Comments
@vuntz I got this idea from /cc @jdsn @bmwiedemann |
aspiers
pushed a commit
to aspiers/automation
that referenced
this issue
Sep 2, 2016
This eliminates the risk of losing crucial debug output in a long mkcloud run because you forgot to redirect to a file and the terminal/screen/tmux scrollback buffer wasn't big enough. Closes SUSE-Cloud#1191.
Nice idea. +1 (for the idea) |
Good idea! This would be quite useful. |
aspiers
pushed a commit
to aspiers/automation
that referenced
this issue
Sep 5, 2016
This eliminates the risk of losing crucial debug output in a long mkcloud run because you forgot to redirect to a file and the terminal/screen/tmux scrollback buffer wasn't big enough. Closes SUSE-Cloud#1191.
aspiers
pushed a commit
to aspiers/automation
that referenced
this issue
Sep 5, 2016
This eliminates the risk of losing crucial debug output in a long mkcloud run because you forgot to redirect to a file and the terminal/screen/tmux scrollback buffer wasn't big enough. Closes SUSE-Cloud#1191.
aspiers
pushed a commit
to aspiers/automation
that referenced
this issue
Sep 5, 2016
This eliminates the risk of losing crucial debug output in a long mkcloud run because you forgot to redirect to a file and the terminal/screen/tmux scrollback buffer wasn't big enough. Closes SUSE-Cloud#1191.
aspiers
pushed a commit
to aspiers/automation
that referenced
this issue
Sep 6, 2016
This eliminates the risk of losing crucial debug output in a long mkcloud run because you forgot to redirect to a file and the terminal/screen/tmux scrollback buffer wasn't big enough. If the 'help' argument is passed, it is assumed that logging is not required. Otherwise, a warning is emitted if logging is not possible due to $cloud not being set. Closes SUSE-Cloud#1191.
aspiers
pushed a commit
to aspiers/automation
that referenced
this issue
Sep 6, 2016
This eliminates the risk of losing crucial debug output in a long mkcloud run because you forgot to redirect to a file and the terminal/screen/tmux scrollback buffer wasn't big enough. If the 'help' argument is passed, it is assumed that logging is not required. Otherwise, a warning is emitted if logging is not possible due to $cloud not being set. Closes SUSE-Cloud#1191.
aspiers
pushed a commit
to aspiers/automation
that referenced
this issue
Sep 7, 2016
This eliminates the risk of losing crucial debug output in a long mkcloud run because you forgot to redirect to a file and the terminal/screen/tmux scrollback buffer wasn't big enough. Closes SUSE-Cloud#1191.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Obviously
mkcloud
needs to retain the ability to output to the CLI, but the same output should also be preserved in a log file for future reference. We could use this trick.The text was updated successfully, but these errors were encountered: