Refer to problem 610215, as the same nonce utility is
After verifying proper operation of the utility
with a few files, I removed the constraints and watched it grind
through some 2000 files, with no outward evidence of any
It turns out that, although the utility listed the
right number of files, and displayed their names in turn, and (I am
certain) performed the two Address System commands (1. read and
process the file to an array; 2. rewrite the file) -- at some point the
files were not actually replaced. I discovered this by running my
application, which tripped over some unrepaired files. Another
run of the Repair utility also seemed to go OK, but, again, a number
of files were not changed. It took about a dozen runs to completely
change all the files!
If Regina is not properly closing those
files, are there not system limits on number of concurrently open
1. Regina should manage its resources better.
Open failures should be reported to the user/application.