Comment 11 for bug 624043

Hi all, hi Trent

thanks for your quick response, but I have to disagree with you. If I restart avahi, everything works until the next reboot, which takes a month sometimes... And the workaround with the pre-start script implies that it is really a matter of which service is started first.

Perhaps I have to clarify, it is not an client-server issue, it's server-only:

I am using a linux box (mythbuntu 10.04 == server) with netatalk and avahi installed to broadcast the shares to my mac clients (a macbook pro with leopard, and a macbook running tiger). If I boot the server normaly, the netatalk-shares are missing in avahi, exactly like micheal has described it. I can access them manually, by connecting to the IP, but this is not what I want...
My impression is that this happens because avahi is started before netatalk in the boot-process. If avahi is started after netatalk (either by restarting it after booting, or by starting netatalk in the pre-start script of avahi), the shares are visible to avahi and correctly advertised. (see the first lines of michaels post, he is running avahi-browse on the server where avahi and netatalk are running, *not* on one of his clients. As soon as avahi sees and broadcasts the shares, all the mac-clients see the shares and everything works as it should, until the system is rebooted.)

The communication between clients and the server has nothing to do with the problem, at least I haven't seen any correlations. Your explanation may be true for a problem where clients can't see shares avahi is broadcasting, but our problem is that avahi itself doesn't see the shares at startup and doesn't broadcast them at all.

Hope now the problem is clear.

Lorenz