| Subject: | PAR does not clean up after itself |
After running PAR during INIT or in user=nobody situations, PAR does not clean up the /tmp/par-SYSTEM cache directory. In fact, it doesn't seem to clean up the cache directories in general (several instances of /tmp/par-root, as well). Because these cache directories potentially contain megabytes of libraries, etc. it's important that PAR cleans itself up afterwards.
If these cache directories are being saved for diagnostic puposes, maybe a compromise could be that if a binary is built with a certain flag, it will retain cache directories.
Also, cleaning up the /tmp/par-* directories after execution prevents leaving corrupt libraries behind.
To summarize:
Issue: PAR does not clean up after itself.
Expected Results: There should be no /tmp/par-* directories after PAR exits.
Actual results: /tmp/par-* contains megabytes of code that shouldn't be left.
Possible solution: Have par clean up after itself, unless the binary was built with a specific flag.
Thanks!
Matt Riedel