Date: Wed, 16 Nov 2011 11:00:27 -0500 (EST) From: Wietse Venema <wietse@porcupine.org> To: Kurt Jaeger <lists@opsec.eu> Cc: freebsd-ports@freebsd.org, Wietse Venema <wietse@porcupine.org> Subject: Re: "postfix-current" broken on amd64 platform Message-ID: <3Sk9KR4s2czk2RT@spike.porcupine.org> In-Reply-To: <20111116140223.GI68080@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3Sk9KR4s2czk2RT>