[avahi] Installation on SuSE 10.0
lennart at poettering.net
Sun Feb 19 13:09:44 PST 2006
On Sun, 19.02.06 20:45, Peter Onion (Peter.Onion at btinternet.com) wrote:
> On Sun, 2006-02-19 at 21:11 +0100, Lennart Poettering wrote:
> > On Sun, 19.02.06 20:59, Sebastien Estienne (sebastien.estienne at gmail.com) wrote:
> > > Maybe we should branch 0.6 and stick to our policy of only bug fix go
> > > in 0.6.x and everything else (new feature) goes in trunk.
> > I don't think this is really necessary. This bug isn't really
> > important or tragic.
> I disagree.... It means you can't easily install avahi-0.6.7 on SuSE
> 10.0 !
Hmm? Did you modify the hosts file? The default hosts file should be
> Ok, well I can do it, but not as easily as you ought to be able to do
> it. You can't start the avahi-deamon using the "enable" button in YaST.
> It doesn't start (see first post in this thread).
This is not a SUSE specific bug. It's pure chance that it has been
triggered with your setup.
> Here's what I've just found.
> If I force static_hosts_load to open /usr/local/etc/avahi/hosts it works
> If I force it to open /hosts it crashes.
Seems your hosts file is invalid in the eyes of the broke
algorithm. Consider removing it.
> Now I'm confused because if the chroot to /usr/local/avahi/etc has
> happened then opening /usr/local/etc/avahi/hosts should not be possible
> and opening /hosts **should work**
If the chroot() was sucessful opening /usr/local/etc/avahi/hosts will
fail. But that is ok, because the file doesn't have to exist. If it
doesn't exist, Avahi won't complain. If the file doesn't exist the
broken parser is not called and everything is fine.
Lennart Poettering; lennart [at] poettering [dot] net
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lennart/
More information about the avahi