-
Notifications
You must be signed in to change notification settings - Fork 95
setGracefulCleanup() doesn't ALWAYS clean up file. #199
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
Comments
@brillout It seems as if 12.2.0 introduced even more changes under the hood. |
@brillout This seems to be what we are experiencing in #198. |
2 tasks
Fixed with #198. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
When using
setGracefulCleanup()
the file should not exist anymore after the process is terminated.Experienced Behavior
setGracefulCleanup()
works when the process receives a SIGINT but doesn't when the signal is SIGTERM or SIGKILL.Same if the the machine were to unexpectedly crash, e.g. the machine's power is shut down.
On linux, the trick would be to create a file and to delete it right away while still having the file open. (As mentioned here.)
Env
[email protected]
The text was updated successfully, but these errors were encountered: