| commit | 3dae2c9f756721a220f8b59c70306031568a3ff2 | [log] [tgz] |
|---|---|---|
| author | Alex Vakulenko <avakulenko@google.com> | Thu Dec 17 11:21:09 2015 -0800 |
| committer | Alex Vakulenko <avakulenko@google.com> | Thu Dec 17 12:03:49 2015 -0800 |
| tree | f48420d91da97121035d9736ce17d9b82e095570 | |
| parent | f1a77fcb460c16e690306ea1e296d26ba7b90da2 [diff] |
Fix avahi host name resolution scenarios When host name collision is detected, avahi picks a new host name, however it fails to update any published services with the new name which leads to wrong IP address resolution for the service. As a work-around, when we detect an avahi-client restart, we just re-publish our service, so it picks up the new host name. BUG: 26237307 Change-Id: I980735890c62957e1bc433a07c319eff646c358c