-
Notifications
You must be signed in to change notification settings - Fork 660
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
Add option to remove scratch dir contents at process exit #230
Comments
See also #165 |
I've uploaded a new snapshot that automatically cleanup the scratch dir. You may want to give a try adding the following var in your env and launch NF as usual.
|
Included in version |
FYI, I tried the production 0.22.3 release (with the ram-disk option), and it seems to have left a bunch of directories and their contents behind in /run/shm :
I'll try /tmp and see if that works differently. |
Double checked and it works as expected. Are you sure you are using the latest version (0.22.3) and that that dirs were not left by a previous run? Check the file
the command before the exit is the one supposed to cleanup the scratch folder. |
I'm seeing the same behavior with scratch = "/tmp" -- the nxf.* directories and their contents are left behind. I'll poke around today and see if I can isolate the problem. I'm running 0.22.3:
System config is Ubuntu Trusty (14.04), with Docker 1.12.1, and SLURM 2.6.5. The only thing that jumped out at me was that the scratch volume is exposed in Docker, as is the /tmp directory itself. Would that be a possibility?
|
That's fine. The container need to work in that dir. You can debug the problem changing into a task work dir, then running |
It would be nice to support ephemeral scratch directories, where the scratch dir is deleted after the process exits (and finishes copying its declared output files.)
The text was updated successfully, but these errors were encountered: