Goetz Neumann wrote:
>
> Jeff Kell wrote:
> >
> > FHarasleben wrote:
> > >
> > > Who has ever seen the following errors (and probably knows what to do
> > > against it):
> > > NETWARE Spawn NCPENGINE: fork ->NCPENGIN<- failed!!
> > >  errno=11 NETWARE Spawn NCPENGINE: fork ->NCPENGIN<- failed!!
> > > : Resource busy, try again
> >
> > I just LOVE plugging away at this error that STILL ISN'T FIXED.
> >
> Now I just love to report, that Jeff is not uptodate on this one :-)
> (Being part of that organisation that deals with bugs day-to-day).
>
> For 5.0 there is the General Release patch: MPEHXT8A,
> for 5.5 there is the Beta Test patch:       MPEHXT8B,
> and the fix is/will be incorporated in the next major release.
>
> Excerpt from the patch text:
> ------------------------------------------------------------------------->
> fork() failed to create a child process when disc space is fragmented.
>
> Currently, when fork() is called to create a child process, the data
> from the parent's HEAP object need to be copied over to the child's
> HEAP object. Due to the generally large amount of data from the HEAP
> that need to be copied, the conventional copy mechanicsm proved to
> be too slow and insufficient. Therefore, a VSM routine, copy_non_
> virgin_pages_of_object, is design solely for this purpose. In order
> to get maximum performance, this VSM routine has a lot of restrictions
> and assumptions. One of the restriction is that the extents of the
> parent HEAP object have to be exactly "cloned" for the child's HEAP.
>
> Now, if the disc space is low or fragmented, the system will have a hard
> time to find a large enough chunk of disc space to allocate the child's
> extents if the parent's extents happen to be created in larger size.
> In this case, fork() will fail with errorno set to eagain (out of system
> resources, try again).
>
> This patch returns to the older algorithm.
> ------------------------------------------------------------------------->
> This text/patch is (if it were) available on the HP support Web as well,
> for the 5.5 BT patch you will have to contact the Response Center.
>
> Hope this helps,
> Goetz.
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=*
> Goetz Neumann         |  email : [log in to unmask]   or
> Hewlett Packard       |          [log in to unmask]
> Worldwide Technolgy   |  http://www.grc.hp.com/documents/PEOPLE/gneumann.html
> Expert Center MPE/iX  |
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=*
Hi Goetz

Tried to get the patch MPEHXT8A from your (HP´s ;) ) WEB side, but I
could not find it there.

Cheers

Friedrich