> I'd like to make sure that no running instance of the script can see an inconsistent state of the install if it's running at the same time as I'm doing the install.
Just an idea and not any proven best practice:
Could you work with two alternate install paths in @INC? Like having a topdir with a timestamp or version or so?
The old CGI would still be using the old path it was started with, and as soon all old instances are gone you can delete the old paths.
Should also be good strategy for fall back if anything goes wrong...
In reply to Re: Install updated version of script such that running instances cannot use an inconsistent state