Application Signals
When client commands (such as hcp) and services are executed by privilege separation, applications in the child process can take advantage of this signal and control the following operations.
The following signals are processed as the signals for service abort. The service will stop the processes of the application at that time, free the resources, and stop the process.
| signal name | description | Windows |
|---|---|---|
| SIGINT | Terminal interruption | ✓ |
| SIGTERM | Terminal end | ✓ |
| SIGUSR1 | USR1 signal |
The following signals are processed as the signals for abort signals based on the resource limit. The service will stop the processes of the application at that time, free the resources, and stop the process.
| signal name | description | Windows |
|---|---|---|
| SIGUSR2 | USR2 signal | |
| SIGXCPU | CPU limit | |
| SIGXFSZ | file size limit |
The following signals are processed as the signals for releasing resources. Right after releasing as many resources as possible (such as the HpFP socket descriptor and so on) and retransmitting (re-raise), the process will stop.
| signal name | description | Windows |
|---|---|---|
| SIGHUP | Hung-up |
Don’t use this signal for child processes, which may cause problems on the entire service running (may need to force-quit the service and restart).
The following signals are ignored.
| signal name | description | Windows |
|---|---|---|
| SIGALRM | Alarm | |
| SIGPIPE | Pipe writing error |
Signals other than these, such as SIGKILL, SIGABORT, and so forth, are not processed (behave following the operation system). Some of the resources may go unavailable (the HpFP socket descriptor and so on).
Don’t use this signal for child processes, which may cause problems on the entire service running (may need to force-quit the service and restart).
Signal numbers can be different depending on the platform. Please refer to each operation system manual.