title: Android init.rc trigger on service-exited
body: <p>I was able to start my own services from the init script (init.rc) in Android, following the guides found at: <a href="http://www.androidenea.com/2009/08/init-process-and-initrc.html" rel="nofollow noreferrer">http://www.androidenea.com/2009/08/init-process-and-initrc.html</a> or with the official documentation found at <a href="https://android.googlesource.com/platform/system/core/+/froyo-release/init/readme.txt" rel="nofollow noreferrer">https://android.googlesource.com/platform/system/core/+/froyo-release/init/readme.txt</a></p>
  
  <p>There is a trigger called "on service-exit-&lt;<em>name</em>>" where <em>name</em> is the name of the service which has to exit before the actions of this trigger are executed. 
  However, this trigger does not seem to work. I started a small shell script as a service and created the trigger accordingly to start all remaining services afterwards. The init process seems to be stuck after the execution of my script and does not continue with the remaining services.</p>
  
  <p>The final goal would be to achieve something like a controlled or 'staged' boot process, where I can make sure that this script is executed first and then the remainnig services are started. I also tried to accomplish that with using different service classes but failed</p>
  
  <p>Any help on that subject is appreciated.</p>