Kbase 17814: Configuring Facetterm Not To Send A Kill -9 To A Process
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
SYMPTOM(s):
Facetterm
User <num> died holding <num> shared memory locks. (2522)
User <num> died with <num> buffers locked. (2523)
Disconnecting dead user <number>. (2527)
CAUSE:
There has been an issue recently brought to our attention with a third party terminal emulation package called Facetterm. Within this emulation package is a configurable option that sends two signals to a process that has not disconnected
successfully or is idle. These are a kill -1 and kill -9 respectively. This has been known to cause the above errors when disconnecting through Facetterm
FIX:
Configuring Facetterm Not To Send A Kill -9 To A Process
After seeing these error messages an abnormal shutdown of the database should follow. This indicates that the user was killed while holding a lock or latch in shared memory, therefore the database shutdown to protect data integrity.
This presents a particular problem for Progress as we are not able to trap a kill -9. It has recently been brought to our attention that there is a configurable option within Facetterm which allows the kill -9 option to be modified. We suggest resetting the second kill to a -1 as well, and Facetterm
Technical Support can give you the exact steps that you need to follow
Progress' official stance on this issue is that we don't support any specific terminal emulators nor can we assist in the altering of any third party product's internal configurations. We have had problems in the past with such products as
Facetterm and now we know that with Facetterm's help you can use a configurable option to alter a potentially fatal behavior of the software with Progress.