** Changed in: oslo Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1263122
Title: services should not restart on SIGHUP when running in the foreground Status in devstack - openstack dev environments: Confirmed Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: As reported on the mailing list (http://lists.openstack.org/pipermail /openstack-dev/2013-December/022796.html) the behavior of the ServiceLauncher has changed in a way that breaks devstack. The work for blueprint https://blueprints.launchpad.net/oslo/+spec /cfg-reload-config-files introduced changes to have the process "restart" on SIGHUP, but screen under devstack also uses that signal to kill the services. That means lots of developers are having to manually kill services to avoid having multiple copies running. To fix the problem we should only restart on SIGHUP when not running in the foreground. There are a few suggestions for detecting foreground operation on http://stackoverflow.com/questions/2425005 /how-do-i-know-if-an-c-programs-executable-is-run-in-foreground-or- background To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1263122/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp