At one point in time, this ["checkin/checkout"] system will cease to exist.Is there any other part of your application that will be able to unambigously detect/determine this time? If so, then can the cleanup code be inserted there? Or could a customer reactivate any checkin/out system at any time in the future?
Even in the latter case, I think you should be able to clean up inactive lockfiles if the cleanup code and the lockfile creation code are both protected by another application-wide lockfile (which never needs to be deleted).
Caveat: I haven't tried any of this out! I hope that my theoretical mullings will be of some use anyway :-)
--
use JAPH;
print JAPH::asString();
In reply to Re^3: File Locking plus delete Lockfile question
by wol
in thread File Locking plus delete Lockfile question
by rovf
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |