Date: Wed, 16 Nov 2011 16:24:23 +0000 From: Chris Rees <utisoft@gmail.com> To: Wietse Venema <wietse@porcupine.org> Cc: Kurt Jaeger <lists@opsec.eu>, Renato Botelho <garga@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: "postfix-current" broken on amd64 platform Message-ID: <CADLo839cfXjJYNJDGb-FhvXMm6sAaFw6Ukf=3akGhquz_DiRfA@mail.gmail.com> In-Reply-To: <3Sk9KR4s2czk2RT@spike.porcupine.org> References: <20111116140223.GI68080@home.opsec.eu> <3Sk9KR4s2czk2RT@spike.porcupine.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16 Nov 2011 16:00, "Wietse Venema" <wietse@porcupine.org> wrote: > > Kurt Jaeger: > > Hi! > > > > > > > > > Postconf opens a socket to determine the mynetworks value (it > > > > > > > determines the local interfaces and their netmasks). > > [...] > > > Postfix does none of that. > > > > The fbsd postfix-current port during the post-install script does > > something which fails on a jail-based build-cluster where the > > jail itself has no network connectivity. > > Would it be possible to give the jail a loopback interface? > > I don't mind if FreeBSD improves its build environment such that > it breaks the build after 12 years. If adding a loopback interface > fixes this, then we can all move on to more interesting things. > > Wietse > Clamav uses loopback on its testing phase, and works fine on the build cluster. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo839cfXjJYNJDGb-FhvXMm6sAaFw6Ukf=3akGhquz_DiRfA>