lockfile kept reappearing

[Walter Vaughan]

Perhaps this may help someone else in the future...

filePro 5.0.14 on FreeBSD 6.1patch10

I was running some end of year reports that print to the /tmp directory.
I'd run a report, try to run a second report, and filePro would complain that 
someone was running an output processing. Well, I'd delete the lockfile, and 
after one report, I'd get same error.

Ran report through debugger, and it counted down okay, and then saw the error of 
my condition when I hit "Q" to make report run at full speed... the /tmp 
directory was full. Sure enough... /tmp at 107% full.

Maybe this is why once in a while in the filePro community you hear of these 
lockfiles that appear without any visible cause... perhaps the output 
location/pipe/device was unable to accept any data, and the lockfile stays set.

--
Walter