OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: Postfix Errors
From: Wietse Venema (wietseporcupine.org)
Date: Thu Dec 21 2000 - 14:25:35 CST

Jason Tuchek:
> Thanks again.
>
> I didn't replace BIND, nor was it ever installed on my system. Postfix is
> not chrooted. My system is a core install w/ the Postfix package added,
> that's it. Nothing has been changed or tampered with (with the exception of
> a few start scripts, shutting off services, etc.).
>
> If you have any more suggestions, they would be greatly appreciated.

Postfix works without error on all Solaris releases that I play
with (2.4, 2.6 and 8.0).

I have done my part of the deal. The problem is local to your
machine.

The number of ways to screw up a complex system like Postfix is
simply enormous - don't use /usr/ucb/cc, don't use LD_XXX_PATH when
compiling or running Postfix, be sure to use Solaris 8 include
files if you installed gcc, 64 bit versus 32 bit. Plenty other
opportunities.

The fact that accept() failed with EACCESS did not ring a bell with
my contact (Casper Dik) who is quite knowledgeable as we all know.

        Wietse

> Thanks.
>
> - Jason
>
> -----Original Message-----
> From: Wietse Venema [mailto:wietseporcupine.org]
> Sent: Wednesday, December 20, 2000 6:04 PM
> To: Jason Tuchek
> Cc: postfix-userspostfix.org
> Subject: Re: Postfix Errors
>
>
> Jason Tuchek:
> > Thanks for your response.
> >
> > I have not done anything to chroot Postfix. If it is chroot'd, then it
> > installed that way, but it doesn't look like it is.
>
> You can find out by examining the master.cf file. Anyway, chroot
> is not the default setting, because it requires so much additional
> setup.
>
> > My nsswitch.conf, and resolv.conf files are in place, and name resolution
> > works fine outside of the Postfix system. So, on this account, I'm at a
> > loss. I'm not sure if everything is setup right, but it seems to be.
>
> OK, I suspect that you have replaced BIND (named) on your system.
>
> The trouble then is that that Postfix was compiled with the BIND
> 8 include files (the files have the same names as the Solaris ones
> that they replaced), and that Postfix was linked with the old
> Solaris libresolv.a library (the BIND libraries have a different
> name).
>
> That is sufficient to completely hose the naming service.
>
> Fix: restore your /usr/include files to the state before you
> installed BIND (fat chance), or link Postfix with the BIND libraries
> that correspond with the new include files.
>
> > As for the other error, thanks for looking into that, I appreciate it.
>
> It may well have to do with the previous one. When you link with
> a library that does not match the include files, memory gets thrashed
> upon left and right, daemons may fly out of your nose, and all
> kinds of impossilble things can happen.
>
> Wietse
>
>
>