-
Notifications
You must be signed in to change notification settings - Fork 292
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
/tmp files don't get cleaned up properly #1973
Comments
The change was recently made it to htmlify And it’s relying on the module to remove the files when it’s done we can easily remove them as we go. I’ll Put that back tomorrow. |
That part has been fixed in 65f77f515a |
Oh, sorry, missed that part. If your fixed is better, just toss mine out. |
Yours is better. I was unlinking them after copying instead |
That commit was all comments; if uncommented, the unlink causes the build to break. (another version with closing the handle before the unlink also breaks the build.) |
So how's this going now? I'm kinda of confused. app.pl deletes its files, htmlify.p6 does not. |
... there were two complaints. one is fixed; the other is not. You can see my attempt in the commits above that had to be backed out because they broke the build. |
Maybe someone can take a look at this? |
Ref #1823 |
The problem
app.pl
leaves behind two files in/tmp
after runninghtmlify.pl6
leaves behind several thousand files if perl is killed before it finishes. Your OS may not be able to clear/tmp
on boot when this happens because there are too many files to pass torm
Suggestions
htmlify.pl6
and removed after the script has finished. This would make removing files on SIGINT/SIGTERM a matter of just catching the signal and removing the entire directoryThe text was updated successfully, but these errors were encountered: