Kbase P118709: proDebugConfig fails when DLC is set to a symbolic link
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.x
UNIX
SYMPTOM(s):
proDebugConfig reports that the debugger security information which controls whether debugging is enabled appears to have been edited with something other than the proDebugEnable tool.
proDebugEnable was run prior to proDebugConfig
The DLC environment variable is set to the path of a symbolic link to the real OpenEdge installation directory
CAUSE:
The value of $DLC is recorded in /etc/ProDbgCK during installation. proDebugEnable and proDebugConfig compare the runtime value of $DLC to the value in /etc/ProDbgCK and fail if they do not match.
If the value of $DLC does not match what is in /etc/ProDbgCK then debugging cannot work. This is how the functionality was designed.
FIX:
As a workaround to this issue, edit the file /etc/ProDbgCK after proDebugEnable and create a new entry with the symbolic link name.
For example, if OpenEdge was installed in /opt/openedge and the symbolic link /opt/dlc is used as DLC instead, do the following:
1. run $DLC/bin/proDebugEnable -enable-all
2. edit /etc/ProDbgCK and add /opt/dlc.status=Debugging enable
Then proDebugConfig will be able to set debugging for client processes.