title: When a Node.js process can exit() directly without triggering other signal events (uncaughtException, SIGINT, SIGTERM...)
body: <p>I work on an application with a REDIS data store. To maintain the data integrity I would like to cleanup the store on process shutdown.</p>
  
  <p>I created a function handler and bind it (with process.on()) to signal events: uncaughtException, SIGINT, SIGTERM, SIGQUIT and it works well (CTRL+C, process killing, exception, ...).</p>
  
  <p>But I've read that in certain conditions the process can exit directly without triggering the other signal events.</p>
  
  <p>The problem in this particular case is that process.on('exit') handler can only process synchronous tasks.</p>
  
  <p>I made different test to try to kill the process in different ways. 
  And (except with SIGTERM on Windows) I wasn't able to identify the case where process.on('exit') is triggered directly without SIGINT, SIGTERM or other event firing.</p>
  
  <p>So my question is (on Linux system), under what conditions the process can exit directly without firing on of this event: <a href="http://nodejs.org/api/all.html#all_signal_events" rel="noreferrer">http://nodejs.org/api/all.html#all_signal_events</a> ?</p>