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

We were wondering the following:

Imaging upgrading nginx by compiling the new version, and doing a make install.

The targets are all the same, essentially the old version is overwritten (we usually pull the configure string from nginx -V).

Is it sufficient to do a nginx -s reload to force the new version of nginx to start being used? Or do we have to kill the process and start it back up?

We are asking this to try and limit downtime as much as possible. I know I know, a quick killall nginx ; nginx.... is a second of downtime... But why have even that second of downtime if it can be avoided.


share|improve this question
up vote 4 down vote accepted

nginx -s reload is not sufficient to upgrade to a new binary. Read this entry on the wiki to see the series of signals that need to be sent to upgrade to a new binary. Alternatively, since you're already installing from source, there's a make upgrade target you can run after make install that will send the signals for you.

share|improve this answer

-s option to reload designed exactly for what you need.

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.