Comment 4 for bug 1334651

Hi Rajesh,

Does nova-api really support SIGHUP? I test it in devstack environment, the last commit of nova is a7e1433a79b30937e29f69a866172c061ced5a5f(Thu Oct 30 00:35:25 2014 +0000).

When I hit "kill -1 $PID_OF_NOVA_API_PARENT" nova-api just log below messages then exit
2014-11-04 08:28:38.520 8249 INFO nova.openstack.common.service [-] Caught SIGHUP, stopping children
2014-11-04 08:28:38.521 8332 INFO nova.openstack.common.service [-] Child caught SIGTERM, exiting
2014-11-04 08:28:38.521 8294 INFO nova.openstack.common.service [-] Child caught SIGTERM, exiting
....
2014-11-04 08:28:38.557 8249 INFO nova.openstack.common.service [-] Child 8294 exited with status 1
2014-11-04 08:28:38.557 8249 INFO nova.openstack.common.service [-] Child 8295 exited with status 1
2014-11-04 08:28:38.557 8249 INFO nova.openstack.common.service [-] Child 8296 exited with status 1
2014-11-04 08:28:38.558 8249 INFO nova.openstack.common.service [-] Child 8322 exited with status 1

But in your environment I believe nova plays very well with SIGHUP, is there some config items to enable this feature? do I missing some thing?