Changes between Version 65 and Version 66 of InternalsDocs


Ignore:
Timestamp:
12/10/14 14:55:57 (2 years ago)
Author:
nkondras
Comment:

Fix SIGKILL spelling

Legend:

Unmodified
Added
Removed
Modified
  • InternalsDocs

    v65 v66  
    217217Apart from the internal SBUS communication, SSSD also uses UNIX signals for certain functionality - either for communication with external utilities or for cases where the SBUS communication might not work, such as an unresponsive worker process. Below is an overview of the supported signals and their use. The singal handlers are typically integrated with the tevent event loop using its `tevent_add_signal` call. 
    218218    SIGTERM:: If a responder or a provider process fails to send a `pong` message to the monitor process after receiving the `ping` message, the monitor terminates the unresponsive process with a SIGTERM. Also used to terminate helper processes (such as the krb5_child process) in case of a timeout.  
    219     SIGKILL:: In cases where an unresponsive worker process does not terminate after receiving SIGTERM, the monitor forcibly kills it with SIGILL 
     219    SIGKILL:: In cases where an unresponsive worker process does not terminate after receiving SIGTERM, the monitor forcibly kills it with SIGKILL 
    220220    SIGUSR1:: Can be handled a sssd_be process individually or the monitor process (in that case, the monitor re-sends the signal to all sssd_be processes it handles). Upon receiving this signal, the sssd_be process transitions into the 'offline' state. This signal is mostly useful for testing. 
    221221    SIGUSR2:: Similar to the SIGUSR1 signal, the SIGUSR2 would cause an sssd_be process to reset the offline status and retry the next request it receives against a remote server.