Re: [BProc] bproc_rfork error

[Erik A. H. <er...@he...>]

On Thu, Oct 18, 2001 at 02:02:33PM -0400, Peter Bowen wrote:
> I'm using BProc 3.1.1 with Red Hat Linux 7.2, and am getting -EIO from
> bproc_rfork when I try to use bpcp.  I patched the glibc with both
> patches, so I'm wondering whether this is the cause, or if it is a known
> bug.  bpsh works just fine, and the nodes are in the error state
> (correct, because the node_up script is failing on bpcp).  I can
> manually make the node up, and is seems to work.

Is this accompanied by messages on the slave console that look
something like "vmadump: mmap failed: <library name>"?

Presuming this is the case....

This is likely some library changes wrt to nodes which are not
"up".  Basically, the library used to check node state and if the
state was not "up" it would use different rfork() flags which
transported all libraries regardless of whether or not they were on
the library list.

With the beoboot that's out there now this was necessary because
libraries aren't present at boot time.  You get and EIO if the undump
fails due missing libraries or whatever.

Since new boot support/library caching stuff can fetch libraries on
demand, the BProc library doesn't do this check anymore.  If bpsh
still works, you must still be using the first dynamic linker hack
which still does that check.

I should have made that an #ifdef or something I guess... at least
until I get LANL beoboot out the door.  That should hopefully be
happening in the next few days since I'm pretty sure I got all the
paper required for that done.  *crosses fingers*

- Erik
-- 
Erik Arjan Hendriks          Printed On 100 Percent Recycled Electrons
er...@he...                   Contents may settle during shipment