title: Linux SystemD Services - Simple vs Forked - Downsides?
body: <p>A lot of programs you download can be run in a blocking manner or in the background (usually by start/stop/etc commands).  Some good examples are HA Proxy and Spring Boot apps built to be Linux services... both can be run in either manner.</p>
  
  <p>In system-d unit files you can use "forked" type to allow you to map to start/stop/etc commands for managing a program that runs in the background/as a daemon.  Alternatively, you can just use the "simple" type and call the app itself in a blocking manner.</p>
  
  <p>Is there any particular reason to prefer "forked" where it is an option?  Having done both options on numerous things, it seems "simple" is lighter on config and more obvious in terms of usage.</p>