bind-8.2.2_p7 chrooted / named-xfer fails (sigpipe)

[Ricardo Manuel Oliveira]

Jim Reid wrote:
> 
> >>>>> "Ricardo" == Ricardo Manuel Oliveira <rmo at eurotux.com> writes:
> 
>     >>  I repeat my first question. Is the version of named-xfer
>     >> that's in the chroot jail the one that is shipped with the
>     >> version of named? You can't use (say) an 8.1 named-xfer with an
>     >> 8.2.2 named.
> 
>     Ricardo> Yes, it is. All of the components come from one same
>     Ricardo> installation, the 8.2.2P7 version. Just in case, this is
>     Ricardo> a redhat RPM, with the necessary modifications (startup
>     Ricardo> parameters) to run in a chroot'ed environment.
> 
> Are you *really* sure the named and named-xfer versions are the same?
> Did you physically check them? Don't believe what the RPM says or
> whoever assembed that RPM. [Personally, I consider RPMs and Linux to
> be just awful, but that's a story for another day.] Check the version
> strings in the binaries and in the comment header in the successfully
> transferred zone files. The SIGPIPE error usually happens when there
> is a version mismatch. That's why I'm convinced that's the problem.

 Hmm, okay. I checked those - md5sum tells me that they are
equal (well, it'd be
a heck of a needle in a haystack to find two matching,
non-equal md5sum'ed files).
 I too share your disgust about RPMs, but that's another
story - this *should*
work, as documented. I'm about to erase the bind
installation and install
a fresh one, if this keeps for more than a few days, so any
help is appreciated.

 Thanks in advance.

----
Ricardo Manuel Oliveira