upgrading binaries with USR2 results in two severs running

[megamic]

Shouldent the original process die after it starts the new process? I
see another server start up, but the old one hang around:

Log:
2010/11/03 07:16:41 [notice] 54825#0: signal 12 (SIGUSR2) received,
changing binary
2010/11/03 07:16:41 [notice] 54825#0: changing binary
2010/11/03 07:16:41 [notice] 54825#0: start new binary process 54951
2010/11/03 07:16:41 [notice] 54951#0: using the "epoll" event method
2010/11/03 07:16:41 [notice] 54951#0: getrlimit(RLIMIT_NOFILE):
1024:1024
2010/11/03 07:16:41 [notice] 54951#0: start worker processes
2010/11/03 07:16:41 [notice] 54951#0: start worker process 54952
2010/11/03 07:16:41 [notice] 54951#0: start worker process 54953

Before:
# ps -ef | grep nginx
root     54825     1  0 18:09 ?        00:00:00 nginx: master process
/opt/local/contrib/sbin/nginx -p /var/log/nginx
www-data 54932 54825  0 18:15 ?        00:00:00 nginx: worker process   
                      
www-data 54933 54825  0 18:15 ?        00:00:00 nginx: worker process   
                      

After:
# ps -ef | grep nginx
root     54825     1  0 18:09 ?        00:00:00 nginx: master process
/opt/local/contrib/sbin/nginx -p /var/log/nginx
www-data 54932 54825  0 18:15 ?        00:00:00 nginx: worker process   
                      
www-data 54933 54825  0 18:15 ?        00:00:00 nginx: worker process   
                      
root     54951 54825  0 18:16 ?        00:00:00 nginx: master process
/opt/local/contrib/sbin/nginx -p /var/log/nginx
www-data 54952 54951  0 18:16 ?        00:00:00 nginx: worker process   
                      
www-data 54953 54951  0 18:16 ?        00:00:00 nginx: worker process

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,147148,147148#msg-147148