-
Notifications
You must be signed in to change notification settings - Fork 251
-
Notifications
You must be signed in to change notification settings - Fork 251
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
Suppressing stderr by default decreases usability #2623
Comments
Note that |
@pcahyna You are right. This does not apply to Seems like I was trained by repeated invocations of |
A practical example. This example is a bit primitive, because in this case ReaR directly uses an
|
Only a quick initial note: I implemented I do not want to spend any more minute of my precious time with Since #2498 Since #2498 Personally I always use I think users who are interested what goes on "behind ReaR's surface" @OliverO2 Should it perhaps be better documented that |
EDIT: Script (4.) corrected. |
In non-debug modes (in particular also in verbose mode) stdout and stderr are redirected to a temporary file STDOUT_STDERR_FILE="$TMP_DIR/rear.$WORKFLOW.stdout_stderr so in non-debug modes stdout and stderr of all programs is still available for the Error function to extract some latest messages cf. #2623
In non-debug modes (in particular also in verbose mode) stdout and stderr are redirected to a temporary file STDOUT_STDERR_FILE="$TMP_DIR/rear.$WORKFLOW.stdout_stderr so in non-debug modes stdout and stderr of all programs is still available for the Error function to extract some latest messages cf. #2623
Stale issue message |
I am aware of #2416. It just does not work for me.
Use Case
I invoke
rear mkrescue
without options. An unexpected problem occurs. I cannot see what went wrong precisely, because relevant error messages are missing in the log file.Edit: As @pcahyna has correctly pointed out, this does not apply to
rear recover
which runs in verbose mode by default.Suggestion
Please do not suppress
stderr
globally. The extra output in the log file seems way more acceptable than seeing a clean log file when actually something bad had happened.The only workaround right now would be to always invoke rear with verbose or debug options. This seems like overkill as in most case just the normal stderr would give a reasonable indication what the problem might have been. Also, increased verbosity makes ReaR harder to use as more lines appear on the terminal, burying possible important messages.
When there are spots which routinely pollute the log file with expected output looking like errors, such spots could be cleaned up individually.
The text was updated successfully, but these errors were encountered: