🚀 go-pugleaf

In article <5934@mccuts.uts.mcc.ac.uk> ehgasm2@uts.mcc.ac.uk (Simon Marshall) writes:
>In article <Bw2pG2.IAz@mach1.wlu.ca> clangfor@mach1.wlu.ca (Carl Langford s) writes:
>
>Nobody is shmallocing huge amounts of shared memory, are they?  I'm not sure if
>this fits your problem, as shbrk() is likely to get stuff from elsewhere, and I
>know nothing about ptx.  But on Dynix, shared memory may be allocated from
>/usr/tmp if it can't get it from $TMPPATH, ./ or ~/ first.  It looks in
>/usr/tmp before /tmp, according to shbrk(p).  It wouldn't show up as a file in
>the file system, of course, you'd have to go poking around to find it.
>
>Hope it's some help, Simon.

The model is different on PTX in that shared memory is not mapped through
the file system anymore. It is mapped directly into swap. /usr/tmp was 
hardcoded into the library routines that front calls to mmap() under 
Dynix 3. Under PTX they appear as 'real' system calls. Would suggest
evaluating paging activity, see vmtune(8).