Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
mb scan/probefile leaves temporary directories behind #16
Issue migrated (2015-06-05) from old issue tracker http://mirrorbrain.org/issues/issue20
msg47 (view) Author: poeml Date: 2009-11-01.22:10:59
drwx------ 2 mirrorbrain mirrorbrain 48 2009-10-31 22:44 mb_probefile__30RC9
These are empty directories, left behind by "mb scan" I think.
msg49 (view) Author: poeml Date: 2009-11-04.20:45:17
While the above was observed on a 64-bit openSUSE 11.0 install, I can't for some reason reproduce it on two other
The temporary directories are created by testmirror.py when it looks up files per rsync.
Given that I understand Python's except..finally statement correctly, the cleanup should always happen, because it is
Thus, it shouls always be executed. There is no reason for errors (shutil.rmtree is recursive, and there is no
All the machines I tested on have Python 2.5, and as far as I know, the finally clause for except..finally was (re-
However, SLE10, where MirrorBrain is deployed extensively as well, there is Python 2.4. So I'm actually not sure why
in the try clause
Replacing the sys.exit(0) with raising an exception, or just removing it, all works correctly.
The only thing that I can imagine is that the backported "processing" module on SLE10 influences the exception
msg66 (view) Author: poeml Date: 2009-11-30.01:00:46
As the problem doesn't occur in most setups, and I can't reproduce it anymore (no
msg100 (view) Author: poeml Date: 2009-12-07.03:18:38
Okay, I'll just close this now.
(end of migrated issue)