Kbase P20976: What signals are trapped and ignored by Progress?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/12/2009 |
|
Status: Verified
GOAL:
What signals are trapped and ignored by Progress?
GOAL:
What signals are trapped by Progress?
GOAL:
What signals are ignored by Progress?
FACT(s) (Environment):
UNIX
Progress 6.x
Progress 7.x
Progress 8.x
Progress 9.x
OpenEdge 10.x
OpenEdge Category: Database
FIX:
There are certain signals that Progress does not handle and they are essentially ignored or may cause the session to terminate.
In Progress 6.3E and below we have handlers on the following signals and the rest are taking default action.
Fatal Signals (Causes _progres to exit)
SIGILL 4
SIGFPE 8
SIGBUS 10
SIGSEGV 11
SIGSYS 12
SIGXCPU 24
SIGXFSZ 25
Signals that cause us to take an action
SIGHUP 1
SIGINT 2
SIGQUIT 3
SIGPIPE 13
SIGALRM 14
SIGTERM 15
SIGTSTP 18
SIGTTOU 22
SIGWINCH 28
SIGUSR1 30
SIGDANGER (if available)
SIGWINDOW (if available)
SIGWIN (if available)
There are signals that we don't trap like:
SIGTRAP 5
SIGABRT 6
SIGEMT 7
SIGKILL 9 (can't be trapped)
SIGURG 16
SIGSTOP 17
SIGCONT 19
SIGCLD 20
SIGTTIN 21
SIGIO 23
SIGVTALRM 26
SIGPROF 27
SIGLOST 29
SIGUSR2 31
In version 6.3F and above our plan is to trap all signals that
we can set handlers on (obviously not 9) and making them behave
like SIGTERM.