Kbase P12369: What should the ownership and the permissions be for the Progress executables on a UNIX platform
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  30/01/2009 |
|
Status: Verified
GOAL:
What should the ownership and the permissions be for the Progress executables on a UNIX platform
FACT(s) (Environment):
UNIX
FIX:
The Progress executables are stored in the bin subdirectory of the Progress installation directory.
Upon a new installation, ownership and permissions are correct.
After the installation of a Patch or Service Pack it's very important that those are reset to their correct value, as the installation might alter them.
Incorrect ownership and/or permissions can cause "abnormal behavior" in the product. One of the first troubleshooting steps should be to always validate the ownership and permissions of all Progress executables are correct.
All executables must be owned by root. Use the chown command to change the owner of a file.
All executables must have permissions 755 (-rwxr-xr-x), with the exception of the following executables, which must have permission 4755 (-rwsr-xr-x).
$DLC/bin/_dbagent
$DLC/bin/_dbutil
$DLC/bin/_mprosrv
$DLC/bin/_mprshut
$DLC/bin/_orasrv
$DLC/bin/_proapsv
$DLC/bin/_probrkr
$DLC/bin/_probuild
$DLC/bin/_progres
$DLC/bin/_prooibk
$DLC/bin/_prooidv
$DLC/bin/_proutil
$DLC/bin/_rfutil
$DLC/bin/dbagent
$DLC/bin/orarx
$DLC/bin/procluster
$DLC/bin/prodb
$DLC/bin/prodebug
$DLC/bin/prolib
$DLC/bin/rpagent
$DLC/bin/rprepl
$DLC/bin/rpserver
$DLC/bin/sqlcpp
Use the chmod command to change the permissions of a file.
Reference your UNIX Operating System documentation for further information on chown and chmod.