Feature Request #265

[librechroot] Support distcc's "+zeroconf"

lukeshu - over 10 years ago - . Updated over 4 years ago.

% Done:



fauno wrote:

feature request: is it possible to run dbus+avahi-daemon on the chroot,
or make it available from the host system? now that avahi is a
dependency of distcc i wanted to try +zeroconf (my build machines are
changing ips a lot lately...) but it couldn't connect to the host avahi.



Updated by fauno over 10 years ago

i'd guess the chroot has to be able to reach dbus...


Updated by mtjm over 10 years ago

This probably can be done using systemd-nspawn and running systemd in the chroot. (I don't like how this makes chroots more complex and build-machine-specific.)


Updated by lukeshu over 9 years ago

  • Subject changed from [librechroot] Optionally start dbus+avahi in the chroot to [librechroot] Support distcc +zeroconf

As a note: For a while now, distcc has been supported in the chroots via the distcc-nozeroconf package, and some hackery with socat and Unix domain sockets.


Updated by lukeshu over 9 years ago

  • Subject changed from [librechroot] Support distcc +zeroconf to [librechroot] Support distcc's "+zeroconf"

Updated by lukeshu about 6 years ago

I believe that connecting /var/run/avahi-daemon/socket to the outside world should mostly do the trick.


Updated by lukeshu over 4 years ago

I don't remember my thought process of the previous comment.

It's only using Avahi to discover hosts, right? Once Avahi tells it about a host, that host will still need rewritten+handled by distcc-tool.


Updated by lukeshu over 4 years ago

  • Tracker changed from Bug to Feature Request

Updated by lukeshu over 4 years ago

What if we just had it run an an avahi query once at startup, to turn "+zeroconf" in to a "manually" configured list?

Also available in: Atom PDF