Thanks to all who responded.....
The short answer is... it's kernel rebuild time. I should have guessed
but the heat in this office is getting to my sensibilities.
Look at the stuff in /sys/conf/YOURNODENAME and all is revealed.
Don't get confused by shell limits but there is a rumour of some
special features if you get my drift ;^)
But... I still don't know why one box chooses to warn that it
cannot unlimit addressspace/vmemoryuse but the others stay mum.
A virtual Beanie Baby for the wiz with the correct answer.
================================================================
O R I G I N A L P O S T I N G
================================================================
>
> I'm getting confused by limit...
>
> When running unlimit one out of many boxes reports....
>
> ... from csh...
>
> % unlimit
> Invalid argument
> unlimit: addressspace: Can't remove limit
>
> ... and from tcsh...
>
> % unlimit
> unlimit: vmemoryuse: Can't remove limit
>
>
> None of the other boxes finds it necessary to report it's inability
> to unlimit addressspace/vmemoryuse.
>
> This appears to be set to...
>
> % limit
> cputime unlimited
> filesize unlimited
> datasize 1048576 kbytes
> stacksize 1048576 kbytes
> coredumpsize unlimited
> memoryuse 1018032 kbytes
> vmemoryuse 1048576 kbytes
> descriptors 4096
>
> ...regardless of the amount of real memory in the box or type
> of box be it a 4100 with 1G or a PW433 with 256M.
>
> Problem.. we need to run an application that requires well over
> 1G of memory.
>
================================================================
k.mcmanus_at_gre.ac.uk -
http://www.gre.ac.uk/~k.mcmanus
-------------------------------------------------------------
Dr Kevin McManus ||
School of Computing & Math Science ||
The University of Greenwich ||
Wellington St. Woolwich ||Tel +44 (0)181 331 8719
London SE18 6PF UK ||Fax +44 (0)181 331 8665
Received on Thu May 27 1999 - 09:49:20 NZST