This repository has been archived by the owner on Jan 30, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 24
Signal handling
Paul Nilsson edited this page Feb 21, 2019
·
1 revision
The Pilot can trap the signals listed in the table below. When such a signal is received, the Pilot aborts the job, data transfer or whatever it is doing at the moment, and informs the server with the corresponding error code.
| Signal | Error code | Meaning |
|---|---|---|
| KILLSIGNAL | 1200 | Job terminated by unknown kill signal |
| SIGTERM | 1201 | Job killed by signal: SIGTERM |
| SIGQUIT | 1202 | Job killed by signal: SIGQUIT |
| SIGSEGV | 1203 | Job killed by signal: SIGSEGV |
| SIGXCPU | 1204 | Job killed by signal: SIGXCPU |
| USERKILL | 1205 | Job killed by user |
| SIGUSR1 | 1206 | Job killed by signal: SIGUSR1 |
| SIGBUS | 1207 | Job killed by signal: SIGBUS |
Note: error code 1205 (USERKILL) is a reserved error code and is currently only defined but handling has not been implemented.