Quoting Friedrich Locke <friedrich.lo...@gmail.com>:
Hi,
i have setted my system resources for a given user via login.conf, but
after the user login the ulimit -a returns different values.
Here is my login.conf entry:
general:\
:coredumpsize=infinity:\
:cputime=infinity:\
:datasize=infinity:\
:filesize=infinity:\
:stacksize=infinity:\
:maxproc=infinity:\
:memorylocked=infinity:\
:memoryuse=infinity:\
:openfiles=infinity:\
:vmemoryuse=infinity:\
:auth=krb5-or-pwd:\
:ignorenologin:\
:localcipher=blowfish,6:\
:ypcipher=old:\
:priority=-5:\
:ftp-chroot:\
:tc=default:
But when i log in, what i get for ulimit is:
sioux@gustav$ ulimit -a
time(cpu-seconds) unlimited
file(blocks) unlimited
coredump(blocks) unlimited
data(kbytes) 8388608
stack(kbytes) 32768
lockedmem(kbytes) unlimited
memory(kbytes) unlimited
nofiles(descriptors) 7030
processes 1310
My doubt is why data and stack limits are not infinity ?
Thanks in advance.
I think this could be because the developers do not want datasize or
stack to be unlimited :)
I do recall reading somewhere in the lists that the maximum amount of
virtual memory that can be allocated by a process using malloc is 8GB
and is set by MAXDSIZ (in vmparam.h). Hopefully I am not giving you a
totally silly answer and someone more knowledgeable will answer your
question correctly.
Vijay Sankar, M.Eng., P.Eng.
ForeTell Technologies Limited
vsan...@foretell.ca
---------------------------------------------
This message was sent using ForeTell-POST 4.9
