Setting wroking directory as READ-ONLY

[bond007jlv]

Are there any potential issues with setting the current working directory for a progress application to READ-ONLY? A client is requesting the application working directory as READ-ONLY for security purposes. The application is started with -T "c:\temp". Does progress dump any temp files directly to the current working directory ignoring the -T startup parameter?

Thank you for your help.

Jose'

 

[tamhas]

Gee, why not make the database read only while you are at it ... that should keep down the errors!

Why not just use a start up script that makes the working directory something private to the user? Then if they ever need to do something like print to disk or run the log utilities, there is a place for their files to go.

 

[TomBascom]

Progress itself will respect the -T setting for its internal temp files (.lbi, .srt, .dbi and so forth...)

There are some optional log files that are created via startup parameters (such as -y and -clientlog) as well as some files that are created by assorted tools that might default to the working directory (for instance the default profiler output goes to the working directory and is named "prof.out"). These could be a problem if you use them with default configurations but SFAIK they can also all be individually redirected to other locations.

On the other hand the application may not. Any "OUTPUT TO" sorts of application code that use the working directory could potentially break if you make the working directory read-only. If you have access to the source you should be able to verify that this is, or is not, going to be a problem. If it is a vendor application then you should ask the vendor.