Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My upstart service is running with the respawn option. I was hoping that if I deploy a new service config, the config will be loaded, when the service respawns. Neither the initctl reload-configuration command forces a reload, nor the restart command. Only an explicit stop and start reloads the configuration.

The problem is, that I can not stop and start the service, at deploy time. The service itself schedules its restart by just shutting down.

Is this behavior by design or am I missing something?

Would it change anything, if I did the respawn with a second watchdog-service by an explicit start if my service stops?

Why is there a difference between an explicit start/stop and the restart command or respawn option.


share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.