Hi Clint, sorry, I most certainly had upstart in my mind when I opened this bug -- so the mistake.
Thanks for the patch, I had bypassed it in a similar way, but not as elaborate. Just one comment -- it is quite rare, I agree, but what would happen if 'cd ${MOUNTPOINT}' fails -- whatever the reason?
Wouldn't it be safer to run the find on ${MOUNTPOINT} (or just plain '/tmp') instead of '.'? There is an implicit risk of data loss here.
Note that this is *not* the issue with the bug, just an additional point. I can open a new bug if you wish.
Hi Clint, sorry, I most certainly had upstart in my mind when I opened this bug -- so the mistake.
Thanks for the patch, I had bypassed it in a similar way, but not as elaborate. Just one comment -- it is quite rare, I agree, but what would happen if 'cd ${MOUNTPOINT}' fails -- whatever the reason?
Wouldn't it be safer to run the find on ${MOUNTPOINT} (or just plain '/tmp') instead of '.'? There is an implicit risk of data loss here.
Note that this is *not* the issue with the bug, just an additional point. I can open a new bug if you wish.