On 12/20/2010 06:22 PM, Eric Blake wrote:
On 12/20/2010 01:03 AM, Laine Stump wrote:
1) Don't attempt to immediately read the pidfile and store the pid in
memory. Instead, just read the pidfile later when we want to kill
radvd. (This could still lead to a race if networkStart and
On 12/20/2010 05:46 PM, Paweł Krześniak wrote:
On Mon, Dec 20, 2010 at 09:03, Laine Stumpla...@laine.org wrote:
There are two possible solutions for this:
1) Don't attempt to immediately read the pidfile and store the pid in
memory. Instead, just read the pidfile later when we want to kill
Running an instance of the router advertisement daemon (radvd) allows
guests using the virtual network to automatically acquire and IPv6
address and default route. Note that acquiring an address only works
for networks with a prefix length of exactly 64 - radvd is still run
in other circumstances,
On Mon, Dec 20, 2010 at 09:03, Laine Stump la...@laine.org wrote:
There are two possible solutions for this:
1) Don't attempt to immediately read the pidfile and store the pid in
memory. Instead, just read the pidfile later when we want to kill
radvd. (This could still lead to a race if
On 12/20/2010 01:03 AM, Laine Stump wrote:
1) Don't attempt to immediately read the pidfile and store the pid in
memory. Instead, just read the pidfile later when we want to kill
radvd. (This could still lead to a race if networkStart and
networkDestroy were called in tight sequence
