transients and tmp files

[ConvertFromOldNGs]

by Andrew >> Sun, 12 Feb 2006 20:40:25 GMT

Just wondering if anyone bothers looking at the tmp files created by jade?

Sure we have transient checking routines that can monitor and log any given process, but occasionally I find myself looking at the build-up of tmp files and wondering...

Which process does each file belong to?
What does the name (.#p321.tmp) of the file indicate?
Are they deleted by Jade at some point?
When is the modified timestamp updated? (some are months old)
Is a 4KB tmp file created for every process?
Do they shrink in size once expanded beyond the initial 4KB?

[ConvertFromOldNGs]

by cnwjhp1 >> Mon, 13 Feb 2006 3:14:36 GMT

The 4k initial size and growth increment are controlled by the TransientDB section of the .ini file. There is one .tmp file per Jade process. They are deleted during normal termination of the process. If you have some with timestamps months old, then either you have had a process running nonstop for a very long time, or (more likely) you had an abnormal termination at some point that killed the Windows process before Jade process cleanup could be done. You can safely attempt to delete the old ones with Windows Explorer - if the process is still running you will not be able to delete it.

I wish there were an easy way to associate the files with processes. Perhaps the file name relates in some way to the numbers inthe jommsg.log, but I wouldn't hold my breath!

If the file keeps growing, you have a transient leak.