9b7a371485
Since radvd 2.0, the daemon does not use daemon_fork() function from libdaemon, but instead calls Linux daemon() function directly. It also passes (1, 1) arguments when logging method (-m) is either stderr (the default) or stderr_syslog. The second argument's value = 1 means that stderr is not closed and left there for (some) log messages. For neutron, it means that corresponding execute() call that spawns radvd and expects the invoked process to close stderr does not ever get completed. The current thread that spawned radvd is locked waiting for radvd to exit, which does not ever occur unless the process crashes or receives a signal. Since L3 agent gives exclusive access to updates queue for each router to one of processing threads only, it means that the thread that got to serve a radvd-powered subnet will not proceed and not update any new ports or other changes to the router anymore. Passing -m syslog makes radvd 2.0+ close stderr and return to execute() caller, proceeding with router update processing. The same arguments should work for old (pre 2.0) versions of radvd too, so passing them unconditionally. We could instead use -m logfile and pass appropriate -l <logfile> argument to radvd to make it log to a log file located in router's namespace storage path. Though that would be not in line with what dnsmasq processes currently do for dhcp agent, where we log all messages to syslog, so sticking to syslog for radvd for consistency. Change-Id: I131db0639bc46d332ed48faa2bbe68a214264062 Closes-Bug: #1398779
# -- Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
# -- External Resources:
The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/
Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/
The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment
For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.