Hello all, Some comments on temporary files, that may (or may not :-) help.
1. Sound programming practices recommend a program to clean up it's own temporary files. AFAIK TB does it. 2. The same programming pratices suggest that a program's temporary files are to be created in a known place (for example, a subdirectory of the system temporary space), and that the user's access controls are to be enforced. 3. But... we all know that things can go wrong. So now kicks in 4. sound sysadmin practices recommend that the system temporary space should be cleared every so often. With that in mind, it seems to me that the best for TB is to create it's temp files under it's own temp space; if this is a multiple user TB, then each user should have it's own private space, and Windows access control should follow the user's permissions. Also, if TB is to use a private temporary space, then... the best is for TB to clean up the temp space on start-up. If TB keeps on using the system temp space, then it's the sysadmin responsibility to create a script to clean it up every so often. -- Best regards, hggdh mailto:[EMAIL PROTECTED]
pgp00000.pgp
Description: PGP signature
________________________________________________________ Current beta is 2.03 Beta/47 | "Using TBBETA" information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
