title: Daemons & applications control
body: <p>This is a duplicate question from here:
  <a href="https://stackoverflow.com/questions/11695138/differences-in-controlling-daemons-applications">Differences in controlling daemons &amp; applications</a>
  only with updated tags so more people 
  can view it and comment.</p>
  
  <hr>
  
  <p>Hi everyone,</p>
  
  <p>With respect to this excellent post:</p>
  
  <p><a href="https://stackoverflow.com/questions/958249/whats-the-difference-between-nohup-and-a-daemon">What&#39;s the difference between nohup and a daemon?</a></p>
  
  <p>I would like to ask the following:</p>
  
  <p>After launching an application from my terminal, the application keeps running either in the background or the foreground and the only thing I can do to interact with it is by sending it signals from my terminal (given that stdin is still in place).</p>
  
  <p>However, after a daemon process is launched, I realized that it can be controlled with other means like querying it or restarting it (arch way):</p>
  
  <p><code># /etc/rc.d/daemon-name {start|stop|restart|status|...}</code> </p>
  
  <p>Could someone explain to me if that feature is built-into the general "daemon framework" and applies to every daemon process as a special feature or is it just a provision that processes designed to run as a daemon will have to handle internally?</p>
  
  <p>And to add more to the matter, how on earth are we able to "control" daemons from the terminal using their name (i.e. sambad stop) while applications always have to be referred using their name (i.e. kill -9 1234)? </p>
  
  <p>Thank you in advance!</p>
  
  <hr>