Remove directories leftover from improper shutdown so sage-cleaner won't kill random processes #35204
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📚 Description
From #27769:
Under rare conditions, sage is killed at startup by sage-cleaner.
This requires:
When sage-cleaner tries to clean up, it will do a "kill 0", which will kill sage.
Files will only be left in ~/.sage/temp/HOSTNAME if sage is not shutdown properly. Most likely because of a reboot.
Even if the situation doesn't result on a "kill 0", sage-cleaner would still go on a killing spree for random processes which is awful.
The current PR removes everything under ~/.sage/temp/HOSTNAME/ at sage-cleaner startup so this doesn't happen.
Since sage-cleaner won't run more than once at a time, this seems safe.
Fixes #27769
📝 Checklist