Rosetta Code

Handle a signal: Difference between revisions

Page Discussion

Handle a signal (view source)

Revision as of 16:52, 1 May 2017

598 bytes added ,  7 years ago
Add SIGQUIT since per the task description SIGQUIT is more appropriate that SIGINT (see perl example) see discussion.
(Add SIGQUIT since per the task description SIGQUIT is more appropriate that SIGINT (see perl example) see discussion.)
Line 14:
{{omit from|XSLT}}
 
Most general purpose operating systems provide interrupt facilities, sometimes called signals either generated by the user or as a result of program failure or reaching a limit like file space.
Unhandled signals generally terminate a program in a disorderly manner.
Signal handlers are created so that the program behaves in a well-defined manner upon receipt of a signal.
 
 
;Task:
Provide a program that displays a singlean integer on each line of output at the rate of about one integer in eachper half second.
<!-- some systems have difficulty with 1/2 second and that's not the point of this subject anyway DG-->
 
Upon receipt of the SigIntSIGINT signal (often createdgenerated by the user typing ctrl-C <!-- on unix see stty -a . on windows SIGBREAK DG -->( or better yet, SIGQUIT ctrl-\ )) the program will cease printingoutputting integers to its, output, print the number of seconds the program has run, and then the program will terminatequit. <!-- outputting the number if seconds is also unduly complicated for this topic . Hope nobody minds these comments and I didn't really want to change the task since there were so many examples already written. see the Perl example for a more extensive use of signals. PS See discussion. If you find these edits inappropriate let me know DG-->
<br><br>
 
Anonymous user
Retrieved from "https://rosettacode.org/wiki/Special:MobileDiff/94337"