Kbase P98603: File created from 4GL ignores umask setting
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/17/2008 |
|
Status: Unverified
SYMPTOM(s):
File created from 4GL ignores umask setting
Using AppServer
File is created in AppServer procedure
File is created using OUTPUT TO statement
File is always created using OS default permissions
FACT(s) (Environment):
UNIX
Progress 9.X
OpenEdge 10.0X
CAUSE:
BUG# 20030313-011
CAUSE:
This is a known issue - The AdminServer is a Java application that runs ( via exec() ) a "C" binary who actually exec's the AppServer broker process. The umask inheritance chain between parent and child processes is broken using this combination of Java and "C" programs. So the default umask value, which is usually set to 022 for the system, is applied when the AppServer broker is exec'd.
FIX:
Starting in 10.1B, you can change the umask in the PluginPolicy section of the AdminServerPlugins.properties file. This is where you can set the file permissions.
[PluginPolicy]
pluginclasspath=
classpath=
policyfile=C:\Progress\OpenEdge101c/java/java.policy
loginconfig=
classloader=java.net.URLClassLoader
jvmargs=
authpolicy=
umask=