Red Hat Bugzilla – Bug 172044
avahi-browse just sits there
Last modified: 2007-11-30 17:11:16 EST
Description of problem:
An attempt of 'avahi-browse -a' or 'avahi-browse -a -d local' produces something
of that sort:
Browsing domain 'local' on any.0 ...
Browsing for services of type '_workstation._tcp' (Workstation) in domain
'local' on eth1.2 ...
Found service 'dyna0 [xx:xx:xx:xx:xx:xx]' of type '_workstation._tcp'
(Workstation) in domain 'local' on eth1.2.
Service data for service 'dyna0 [xx:xx:xx:xx:xx:xx]' of type '_workstation._tcp'
(Workstation) in domain 'local' on eth1.2:
Host dyna0.local (192.168.yy.yy), port 9, TXT data:
output stops and nothing happens anymore. One can only break-out with ctrl-C.
Is this really an exected behaviour?
Version-Release number of selected component (if applicable):
This is expected behaviour. mDNS is a long-running operation, and the app will
print any dynamic changes on the network.
Hm, maybe this behaviour is really expected but does that mean that zeroconf
attempts may also last for a very long time? Does not sound overly useful.
By definition they last indefinately, until you cancel them. That is part of the
design, which is to allow a dialog to keep displaying an up-to-date list of the
services availible on the network.