Ticket #664 (closed defect: fixed)
Scripts error code attribution
| Reported by: | nrueff | Owned by: | nrueff |
|---|---|---|---|
| Priority: | High | Milestone: | 1.2.3 |
| Component: | pulse2-launchers | Version: | 1.2.1 |
| Severity: | Minor | Keywords: | |
| Cc: |
Description (last modified by nrueff) (diff)
The following error code convention has to be used:
- 0: success
- 1 to 199: script error (on the client)
- 200 to 231: script was killed by signal "code-200", 200 meaning a signal higher than 31 (SIGSYS) was sent (most probably a RT signal)
- 232 to 239: kept for future usage (unused)
- 240 to 254: pre-check script error (original error code: "code-240"), 240 meaning that something weird append while pre-checking
- 255: connection was impossible.
The wrapper has to be modified to handle this new convention.
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
