abrt-console-notification.sh error if noclobber is set: abrt/lastnotification.<TMP_SUFFIX>: cannot overwrite existing file #1371
Projects
Comments
|
D'oh, did it print out the error message to your terminal? (I tried so hard to mute all errors). The command should create a file holding the date of the last notification. The script tries to robust, so it first creates a temporary file and if it succeeds, it adds the content. The failing command can be replaced with The redirects should be swapped to avoid errors being printed out - i.e. first |
|
Note for myself - what is noclobber: |
ernestask
added a commit
that referenced
this issue
Jun 8, 2020
If the goal is to prevent any kind of error leakage to the user, then stderr redirection must come first. #1371
ernestask
added a commit
that referenced
this issue
Jun 8, 2020
When using bash and when noclobber is set on the parent shell, trying to write out the current time will fail every time. We can instead append to the file and read the last line instead, in case moving fails as well. Fixes #1371
mgrabovsky
pushed a commit
that referenced
this issue
Jun 8, 2020
If the goal is to prevent any kind of error leakage to the user, then stderr redirection must come first. #1371
mgrabovsky
pushed a commit
that referenced
this issue
Jun 8, 2020
When using bash and when noclobber is set on the parent shell, trying to write out the current time will fail every time. We can instead append to the file and read the last line instead, in case moving fails as well. Fixes #1371
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This in abrt/src/cli/abrt-console-notification.sh:
fails if noclobber has been set. If $TMPPATH points to a file to be replaced, it should be removed explicitly first.
The text was updated successfully, but these errors were encountered: