You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Besides the obvious problem of seeing the same IP address twice, the problem is there is no stability in the xenstore path for a given IP address: a client using xs_watch() here on vif/0/ipv4/1 would get a spurious wake when it disappears, and would have to spend CPU cycles with more code just to find out if the iface has been brought down, and to locate the new path if not.
The text was updated successfully, but these errors were encountered:
Here is what we see when removing the IP recorded as "first one" by the tool:
initially:
after removal of the IP with
ip addr add 172.16.210.109 dev eth0
, after a delay due to periodic polling we get:and after some more time finally:
Besides the obvious problem of seeing the same IP address twice, the problem is there is no stability in the xenstore path for a given IP address: a client using
xs_watch()
here onvif/0/ipv4/1
would get a spurious wake when it disappears, and would have to spend CPU cycles with more code just to find out if the iface has been brought down, and to locate the new path if not.The text was updated successfully, but these errors were encountered: