Hi Mr Szilagyi
Even when we put the vmemoryuse unlimited we get 524288, and here is the
results of swap -l and swap -s.
indigo% swap -l
lswap path dev pri swaplo blocks free maxswap vswap
2 /.swap.virtual
128,16 2 0 0 0 0 600000
1 /dev/swap
128,17 0 0 260696 260696 260696 0
indigo% swap -s
total: 0.00k allocated + 63.27m add'l reserved = 63.27m bytes used, 480.90m
bytes available
indigo% limit
cputime unlimited
filesize unlimited
datasize 524288 kbytes
stacksize 65536 kbytes
coredumpsize unlimited
memoryuse 122308 kbytes
descriptors 200
vmemoryuse 524288 kbytes
Thank you very much
Andras Szilagyi wrote:
> On Tue, 04 May 1999 14:55:16 GMT, A. Khiat <khiat at sympatico.ca> wrote:
>> >Here are the parameters when the "limit" command is typed:
> >cputime unlimited
> >filesize unlimited
> >datasize 524288 kbytes
> >stacksize 65536 kbytes
> >coredumpsize unlimited
> >memoryuse 122308 kbytes
> >descriptors 200
> >vmemoryuse 524288 kbytes
> >
> >memoryuse becomes 524288 when the unlimited command is typed.
>> Please enter all the following commands:
> limit vmemoryuse unlimited
> limit memoryuse unlimited
> limit datasize unlimited
> limit stacksize unlimited
>> and then try to run InsightII again.
>> If it is killed again, the most likely cause is that the virtual memory
> is too small. Look at what the "limit" command reports for vmemoryuse
> (after setting it to "unlimited"). On our machine, it reports 2097152
> kbytes, i.e. 2 gigabytes, and InsightII 97.0 works for us. You should
> configure the virtual memory as it is described in the Installation Guide
> that comes with InsightII.
>> >What really intrigues us is that the InsightII 400 version is fully
> >operational.
> >Are the requirements for the 970 version that different??
>> I don't know but that is fairly possible.
>> Andras
