Xref: utzoo news.admin:5419 news.software.b:2147 unix-pc.general:2593
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!tut.cis.ohio-state.edu!osu-cis!att!icus!lenny
From: lenny@icus.islp.ny.us (Lenny Tropiano)
Newsgroups: news.admin,news.software.b,unix-pc.general
Subject: Re: pathalias problem: out of memory type error
Summary: How did you get that much memory for all the maps?!
Message-ID: <654@icus.islp.ny.us>
Date: 4 Apr 89 17:29:31 GMT
References: <459@flatline.UUCP>
Reply-To: lenny@icus.islp.ny.us (Lenny Tropiano)
Distribution: usa
Organization: ICUS Software Systems, Islip, New York
Lines: 59

In article <459@flatline.UUCP> erict@flatline.UUCP (J. Eric Townsend) writes:
|>
|>Well, here's the error:
|>pathalias: out of memory (2460k allocated); notify the authorities
|>
|>
|>I have this sneaking suspicion that I can only allocate 2460k per
|>process under my flavor of unix. (3b1 Unix 3.0, kinda like Sys V rel 0.0).
|>
|>Any hints/solutions?

This is strange.  On my UNIX pc, I'm running a pathalias every night, after
it runs uuhosts -unbatch (which unbatches new posted maps safely).  I'm
running 3.51 (actually a variant thereof) and pathalias'ing all the 
d.*, u.*, and my local map.* files.  This is the output I get, which
incidently has been working fine here for decades (well 2 years actually):

rehash into 2039
rehash into 3067
rehash into 5113
rehash into 8179
rehash into 13309
rehash into 21499
rehash into 34807
16997 vertices, 39445 edges
allocation is 1408k after parsing
*** mapping
heap high water mark was 5610
498 backlinks
heap high water mark was 498
7 backlinks
heap high water mark was 9
0 backlinks
You can't get there from here:
	ideia
	.labein.es
	obelix
	eupa.upv.es
	labein.es
	.nsi.es
	nsi
allocation is 1480k after mapping
allocation is 1480k after printing
memory allocator wasted 1980 bytes

This is only 1480k, not 2460k?  What are you trying to pathalias?
Granted I have 3.5MB in my machine ... that might have something to do
with it ;-)   I thought the only limit on this virtual memory machine was
the size of the swap space, after you allocated too much, it would fill
the swap space up and then die (this has happened to me).  I've also
gotten "Killed" when trying to start compresses when my system is utilizing
lots of memory.

-Lenny
-- 
Lenny Tropiano             ICUS Software Systems         [w] +1 (516) 582-5525
lenny@icus.islp.ny.us      Telex; 154232428 ICUS         [h] +1 (516) 968-8576
{talcott,decuac,boulder,hombre,pacbell,sbcs}!icus!lenny  attmail!icus!lenny
        ICUS Software Systems -- PO Box 1; Islip Terrace, NY  11752