Kbase P126300: Client executable (_progres) does not terminate when user exits the application.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/10/2007 |
|
Status: Unverified
FACT(s) (Environment):
UNIX
SYMPTOM(s):
_progres session does not terminate when user exits the application.
Terminating client session by selecting X on the telnet window.
Terminal emulator being used is TinyTERM
Can duplicate the issue using Putty terminal emulator
Cannot duplicate the issue outside of the application.
Database log file <dbname.lg> does not show that Database Server is receiving any signals associated with that client process when initiated via the application.
Application being initiated via a script.
CAUSE:
The script used to invoke the application contains a trap command. The trap command being issued within the script is:
trap : 1 2 3
This trap command results in the current shell ignoring / executing the null command. All active sub-shells however will be terminated. The script was invoking the _progres executable within the same shell and therefore the signal was being ignored.
FIX:
Remove the UNIX trap command from scripts used to invoke _progres or any other Progress/OpenEdge executables.
If the trap command is required for some UNIX administrative reason, then alter the script to ensure that Progress/OpenEdge executables are not blocked from receiving a signal. In this situation, invoking _progres within a sub-shell would result in the _progres executable terminating appropriately.