sigint ctrl c

In the performance test, the tester program is started by the start. Sh script. Now, the user needs to press Ctrl-C to exit the program graceful without restarting the board. The problem is: Ctrl-C generates a signal SIGINT, but this signal is

First, the background process Management commandFG, BG, Jobs, &, CTRL + Z, CTRL + C, CTRL + \, CTRL + D1. &Add to the end of a command, you can put this command in the background to perform, such as Firefox &2, CTRL + ZYou can put a command that is

First, the background process Management command FG, BG, Jobs, &, CTRL + Z, CTRL + C, CTRL + \, CTRL + D1, &At the end of a command, you can put this command in the background, such as GFTP,2, CTRL + ZA command that is executing in the foreground

SIGHUP terminating process terminal line hang-offSIGINT terminating process Interrupt processSigquit establish core file termination process, and generate core fileSigill Creating a core file illegal directiveSIGTRAP build core file tracking

Sigterm is a signal that a kill sends without parameters, meaning that the process terminates, but execution depends on whether the process is supported or not. But unlike Sigkill signals, it can be captured and interpreted (or ignored) by the

FG, BG, Jobs, &, CTRL + Z are all related to system tasks, although these commands are largely not needed now, but they are also usefulOne. & is most often usedThis is used at the end of a command, you can put this command in the background to

Turn from: http://blog.csdn.net/fengyifei11228/article/details/5737371 http://idas643.blog.163.com/blog/static/167104838201341493846584/ First, the background process Management command FG, BG, Jobs, &, CTRL + Z, CTRL + C, CTRL + \, CTRL + D1, &At

SighupSIGINT terminates process interruptionSigquit creates a core file to terminate the process and generates a Core FileInvalid Command for creating core file in sigillSigtrap creates core file tracking self-trapsSigbus Core File bus creation

1. sigterm "Kill PID" sends sigterm to the process PID. This is the termination signal sent by killcommand by default. 2. SIGINT Hitting the interrupt key (delete or Ctrl + C) in the terminal generates a SIGINT signal. This signal will be sent

All three are end/terminate process runs.1.SIGINT sigterm DifferenceThe former is associated with the character Ctrl + C, which does not have any control character associations.The former can only end the foreground process, while the latter is