Unfortunately the lock not always released thus stopping further executions of the program (and any other programs that rely on the same lock). The only way to remedy this is to ftp the server and delete the lockfile.Does that mean the program just doesn't end, or that it ends without releasing the lock?
If the latter, try putting the untie() and close() statements in the END block of the program.
If the former, you might have to fork off the process and keep an eye on the time it takes to run from the parent...
OR, you could save the PID of the program in another file, and kill it if it has run for too long (also remove the lock), the next time you have to have access to the DB.
Ofcoure, the last 2 methods might be very unsafe for your data....
Hope this helps,
Joost.
In reply to Re: pesky lockfile stays locked
by Joost
in thread pesky lockfile stays locked
by traxlog
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |