showard@uccba.UUCP (Steve Howard) (06/23/87)
I am running SYSV R2 on an AT&T 3B2. I am attempting to run pathalias
(From the Jan 86 posting) without any luck. When I feed the whole
map to pathalias I get the following on standard error:
rehash into 2039
pathalias: rehash error
pathalias: cannot recover!
When PA is only fed a state or two it runs but says "you can't get there
from here" and lists several @ signs. But if I feed it all the "d."
files it fails.
Is there some kind of problem allocating memory? I tried running PA at
night with no load, and it crashed with about 1.5 Meg of memory free
and no swap space used!!!! (according to sar -r). At this poing I
figured that there was some sort of per-process-limit of memory usage.
My kernel and shm values are as follows:
4096 MAXUMEM max. pages in users virtual address space
4096 MAXMEM similair to above
1 MAXSC max number of pages swapped out (not documented by AT&T!!!)
1 MAXFC number of pages saved (not documented by AT&T)
131072 SHMMAX max shared mem seg size
100 SHMMNI shared memory identifiers
6 SHMSEG max attached shm seg per process
512 SHMALL max in use shared mem (not used according to Rel Notes)
All the parameters were changed up and down and even to the values suggested
in the manual (probably a mistake :-)). Nothing changed.
As a last resort I undefined MYMALLOC and tried again. No change.
Am I missing something here?? Any comments or suggestions would be
appreciated.
--
Steve Howard UUCP: {pyramid,philabs!phrimit-eddie}!uccba!showard
USPS: M.L. 130, Cincinnati, OH 45221john@uw-nsr.UUCP (John Sambrook) (06/23/87)
In article <1177@uccba.UUCP> showard@uccba.UUCP (Steve Howard) writes: > >I am running SYSV R2 on an AT&T 3B2. I am attempting to run pathalias >(From the Jan 86 posting) without any luck. When I feed the whole >map to pathalias I get the following on standard error: > >rehash into 2039 >pathalias: rehash error >pathalias: cannot recover! > >When PA is only fed a state or two it runs but says "you can't get there >from here" and lists several @ signs. But if I feed it all the "d." >files it fails. > >Is there some kind of problem allocating memory? I tried running PA at >night with no load, and it crashed with about 1.5 Meg of memory free >and no swap space used!!!! (according to sar -r). At this poing I >figured that there was some sort of per-process-limit of memory usage. There was a bug in our version of pathalias in function yylex() in file parse.y. There is a declaration of "char buf[BUFSIZ]" that needed to be made static as the contents of the buffer are used after the function has returned. You should check to see if this is the case in your version of pathalias. I found this bug when I ported pathalias to our Data General MV/10000 system; others have found it on the 3B series as well. Good luck. >Steve Howard UUCP: {pyramid,philabs!phrimit-eddie}!uccba!showard > USPS: M.L. 130, Cincinnati, OH 45221 -- John Sambrook Dial: (206) 545-7433 University of Washington WD-12 Inet: john@nsr.acs.washington.edu Seattle, Washington 98195 UUCP: uw-nsr!john