Kbase 20768: Group ID for broker is not set correctly within Progress 9.x & WebSpeed 3.x
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/12/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.x
WebSpeed 3.x
Caldera Open UNIX/SCO UnixWare
Compaq Tru64 UNIX
HP-UX
IBM AIX
SCO OpenServer
Sun Solaris SPARC
SYMPTOM(s):
Application can not acess files
Application is set to access files with specific GROUP ID
At the OS level, the Process ID of the broker does not reflect the GROUP ID set for the broker
GROUP ID for broker set correctly within ubroker.properties file
Process ID of the broker reflects the GROUP ID of the Adminserver
An example of the problem:
Broker GROUP ID = admin.
Adminserver GROUP ID = SYS.
At the Unix level, the process ID of the broker shows SYS.
CAUSE:
This behavior is an operating system issue, not a Progress issue.
In general, UNIX systems only allow users to set the group to either the calling process/user's group ID (in this case, the AdminServer), or to the group ID of the executable (_progres, _proapsv, etc..). UNIX does not allow you to change the group ID to anything else.
FIX:
If the user would like to set the group ID of the agents, then the set-group-id bit must be enabled.
Follow these steps to set the set-group-id bit ON:
1) Change the server executable GROUP ID to the desired group.
Refer to your broker configuration for the server executable name (_progres for WebSpeed, _proapsv for AppServer, etc).
2) Turn the set-group-id bit on.
chmod g+s <executable-name>
3) Set the Group property at the specific broker configuration to the same group that the executable was set to in Step 1., Step 3 does not need to be done for Linux Intel systems.