IronBits
08-26-2003, 09:44 AM
Upon getting a fatal error, the client sometimes stays in memory occupying anywhere from 15-35mb, sometimes there is a CMD window still running that will go away if you kill this roque client process, sometimes not.
What happens next, is what contributes to the filelist.txt file is corrupt, please create a new one error.
dfGUI, or task scheduler, or whatever you use to check on the client to make sure it's running by looking for the *.LOCK file, find it missing and restart the client, the 1st one is still there locked on the open files, so the 2nd process can't do much and corrupts the filelist.txt.
Howard, when running -qt mode, could you put the error message in the error.log and make sure the client exits cleanly under all fatal error conditions?
I have seen this many times, and it also leaves all 4 files in the TEMP directory when this happens.
some number.cdx
some number.dbf
some number.fpt
some number (with no extension)
What happens next, is what contributes to the filelist.txt file is corrupt, please create a new one error.
dfGUI, or task scheduler, or whatever you use to check on the client to make sure it's running by looking for the *.LOCK file, find it missing and restart the client, the 1st one is still there locked on the open files, so the 2nd process can't do much and corrupts the filelist.txt.
Howard, when running -qt mode, could you put the error message in the error.log and make sure the client exits cleanly under all fatal error conditions?
I have seen this many times, and it also leaves all 4 files in the TEMP directory when this happens.
some number.cdx
some number.dbf
some number.fpt
some number (with no extension)