Comment 8 for bug 624043

Hi there!

I definitetly think this is not a duplicate of bug #327362, because this one is only a matter of which daemon is started when, i.e. avahi has to be started/restarted *after* netatalk in order to advertise these services properly. There is a thread in a german forum which describes the problem, and a possible workaround involving a pre-start script. Somebody commented that the problem starts only if samba sharing is activated, but I think this is not a necessary condition.

http://forum.ubuntuusers.de/topic/samba-und-netatalk-avahi-kommen-sich-ins-gehe/#post-2298101

The workaround to add the following lines to /etc/init/avahi-daemon.conf fixes the problem at boottime but raises others, because this prevents avahi from being (re)started if netatalk is already running.

pre-start script
    /etc/init.d/netatalk start
end script

Solution 1: One adds 2 lines of code to the pre-start script which check wheather netatalk is running during the start of avahi, and only execute "/etc/init.d/netatalk start" it if needed. This should be easy but is a little dirty I think, because this implies that actually not the boot process triggers the start of netatalk, but avahi does.

Solution 2: One diggs a bit deeper in the upstart-thing, which I do not know at all, and moves the start of avahi towards the end of the boot-process. This is the better solution I think, but I still start and stop my daemons with /etc/init.d/.... start/stop and ignore the "this has been converted to an upstart job" message, so I have no clue how upstart works and how much work this might be...

Lorenz

PS: is it possible to "un-duplicate" this Bug, since it isn't a problem with the .local domains?