sigint

We always want to classify unknown events. When it happens, pass a piece Code Is the easiest solution, that is, we want to process code like processing data. A new process object can be created through proc: Ruby> quux = proc {| Print "quuxquuxquux !!! \ N"|}# Now, quux points to an object. Like other objects, it can also be called. In particular, we can use the call method to execute it: Ruby> quux. CallQuuxquuxquux !!!Nil Can quux be used as a method parameter? Of course. Ruby>

Traditionally, the system signal is the control signal transmitted by the system to the process. For example, SIGINT and sigterm. The transmission of these signals usually indicates the relevant process to complete the corresponding operation, or suspend or terminate, or some other operations. In tor systems, there are two types of signals: traditional signals and controller signals. BelowCodeSection is a simple list of these signals: /* These signal

externally using the KILL command, typically a job control signal such as SIGINT, SIGHUP, then all threads are traversed until a thread that does not block the signal is found and then called to process. (typically found from the main thread), note that only one thread can receive it. Second, each thread has its own separate signal mask, but all threads share the signal action of the process. This means that you can call Pthread_sigmask (not sig

$ Kill-l1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL5) SIGTRAP 6) SIGABRT 7) SIGBUS 8) SIGFPE9) SIGKILL 10) SIGUSR1 11) SIGSEGV 12) SIGUSR213) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGSTKFLT 17) SIGCHLD18) SIGCONT 19) SIGSTOP 20) SIGTSTP 21) SIGTTIN22) SIGTTOU 23) SIGURG 24) SIGXCPU 25) SIGXFSZ26) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGIO30) SIGPWR 31) SIGSYS 34) SIGRTMIN 35) SIGRTMIN + 136) SIGRTMIN + 2 37) SIGRTMIN + 3 38) SIGRTMIN + 4 39) SIGRTMIN + 5

; //////////////////////////////////////// //////////////////////////////////////// //////////// // Function: sig_brk (), signal handle, close deviceHandle then exit, if press CTL-C or CTL -\ // Param: signo, the signal number // Return: void //////////////////////////////////////// //////////////////////////////////////// //////////// Static void Sig_brk (int signo) { If (sig

. The result is as follows: [purple@localhost review]$ gcc test.c[purple@localhost review]$ ./a.out^Csig_num: 2select: Interrupted system callhello world!hello world! Because SIGINT has been registered through signal (2, handler);, it is clear that after pressing ctrl + c, the signal processing function handler will naturally capture this signal, therefore, ^ Csig_num: 2 is displayed. The select function processes the interrupt signal. When an interru

signal is used to notify it to reread the configuration file.2) SIGINTA program termination (interrupt) signal, issued when the user types the intr character (usually ctrl-c), to inform the foreground process group that the process is terminated.3) SigquitSimilar to SIGINT, but controlled by the quit character (usually ctrl). The process generates a core file when it receives a sigquit exit, similar to a program error signal in this sense.4) SigillAn

signal is used to notify it to reread the configuration file.2) SIGINTA program termination (interrupt) signal, issued when the user types the intr character (usually ctrl-c), to inform the foreground process group that the process is terminated.3) SigquitSimilar to SIGINT, but controlled by the quit character (usually ctrl). The process generates a core file when it receives a sigquit exit, similar to a program error signal in this sense.4) SigillAn

#include #include#includestring.h>#include#include#includevoidCatch_signal (intSign ) { Switch(sign) { CaseSIGINT://SIGINT default behavior is to exit the processprintf"SIGINT signal\n"); Exit (0); Break; CaseSIGALRM://SIGALRM default behavior is to exit the processprintf"SIGALRM signal\n"); Break; Casesigkill:printf ("SIGKILL signal\n"); Break; }}//It is recommended to use the mysignal after encaps

void func (int), or the following special value: sig_ign : Ignore signal SIG_DFL : Default behavior for recovering signals Say so much, or give an example to illustrate, the source file is named signal1.c, the code is as follows:#include The results of the operation are as follows:As you can see, the first time you press the abort command (CTRL + C), the process is not terminated, and the polygon is the output ouch! -I got signal 2, because the default behavior of

(IP,0,sizeof(IP)); Inet_ntop (af_inet, AMP;ADDR-GT;SIN_ADDR.S_ADDR, IP,sizeof(IP));printf("Server: (Client Address:%s (%d) connected) \ n", IP, port2);}voidDo_service (intCFD) {LongT = time (0);Char* s = ctime (t); size_t size =strlen(s) *sizeof(Char);if(Write (CfD, S, size)! = size) perror ("Write error");}intFdvoidSig_handler (intSIG) {if(sig = = SIGINT) {Close (FD);Exit(1); }}intMainvoid){if(Signal (SIGINT