Very Computer

> If I do a ulimit -a

> # csh
> # ulimit -a
> time(seconds)        unlimited
> file(blocks)         unlimited
> data(kbytes)         131072
> stack(kbytes)        8192
> memory(kbytes)       366880
> coredump(blocks)     unlimited
> nofiles(descriptors) 4096
> vmemory(kbytes)      4194304

> What parameters do these map to ?

> Is it the kernel parameters in proc :-
> # sysconfig -q proc
> proc:
> per_proc_stack_size = 8388608
> per_proc_data_size = 134217728
> per_proc_address_space = 4294967296

> Thanks
> Andrew

> > If I do a ulimit -a

> > # csh
> > # ulimit -a
> > time(seconds)        unlimited
> > file(blocks)         unlimited
> > data(kbytes)         131072
> > stack(kbytes)        8192
> > memory(kbytes)       366880
> > coredump(blocks)     unlimited
> > nofiles(descriptors) 4096
> > vmemory(kbytes)      4194304

> > What parameters do these map to ?

> > Is it the kernel parameters in proc :-
> > # sysconfig -q proc
> > proc:
> > per_proc_stack_size = 8388608
> > per_proc_data_size = 134217728
> > per_proc_address_space = 4294967296

> > Thanks
> > Andrew

> yep,

> and max-xxxx in sysconfig is the value you'll get if you ulimit
> something to unlimited.
> in Version 4.X, you should change maxvas in vm subsystem along with
> max per proc address space.