Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Nov 2011 08:03:10 -0500 (EST)
From:      Wietse Venema <wietse@porcupine.org>
To:        Kurt Jaeger <lists@opsec.eu>
Cc:        wietse@porcupine.org, freebsd-ports@freebsd.org
Subject:   Re: "postfix-current" broken on amd64 platform
Message-ID:  <3Sk5Nt4sX9zk2RT@spike.porcupine.org>
In-Reply-To: <20111116125242.GH68080@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).
> 
> [quote
>  http://archives.neohapsis.com/archives/postfix/2011-11/0385.html]
> > > >   I have heard about bizarre errors on FreeBSD (jail) systems where
> > > > the user-land library was out of sync with kernel-land, resulting
> > > > in data structure mis-matches and system calls returning
> > > > nonsensical results.
> 
> > > Is it a clever idea to hardcode local interfaces on build machine
> > > into a package that will then be redistributed to other machines?
> 
> No.

Postfix does none of that. 

Can someone please explain what socket call is failing, and what
the reasons for that might be? 

I tend to believe that network-less build environments are not
representative for the environment where an Internet MTA would run,
but hey, what do I know.

	Wietse



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3Sk5Nt4sX9zk2RT>