Opened 15 years ago
Closed 15 years ago
#63 closed task (fixed)
Signal handling
Reported by: | kilian | Owned by: | kilian |
---|---|---|---|
Priority: | P1 | Milestone: | v2.0.1 |
Component: | core | Version: | 2.0.0alpha |
Severity: | blocker | Keywords: | |
Cc: |
Description (last modified by )
Implement signal handling (as in W1).
Change History (6)
comment:1 Changed 15 years ago by
Description: | modified (diff) |
---|---|
Summary: | Signals and run management → Signal handling |
comment:2 Changed 15 years ago by
Milestone: | v2.0.0final → v2.0.1 |
---|
comment:3 Changed 15 years ago by
Priority: | P4 → P2 |
---|
comment:4 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
The resolution I have implemented in r2385:
- Signals SIGINT, SIGTERM, SIGXCPU, SIGXFSZ are masked during execution of WHIZARD (in the main program)
- At certain breakpoints, the program checks whether signals have been set and terminates gracefully
I used a C wrapper around sigaction(2) which appears to be POSIXly correct. Should be checked on the MAC.
comment:5 Changed 15 years ago by
Priority: | P2 → P1 |
---|---|
Resolution: | fixed |
Severity: | normal → blocker |
Status: | closed → reopened |
Seems that the C wrapper files have not been included in the trunk. They break even make.
comment:6 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
This was a bogus alarm. A make was not mighty enough, needed a autoreconf and new configure.
Note: See
TracTickets for help on using
tickets.
Should be more important now.