Stuart Henderson <s...@spacehopper.org> writes: > On 2012/04/20 22:44, Kostas Zorbadelos wrote: >> Stuart Henderson <s...@spacehopper.org> writes: >> >> > On 2012-04-20, Kostas Zorbadelos <kzo...@otenet.gr> wrote: >> >>> Also, per process limits play a role. >> >>> >> >> >> >> Does named has such a limit by default? >> > >> > OpenBSD has a limit by default, see login.conf(5). Daemons started >> > when the system is booted or using /etc/rc.d scripts typically use >> > the class 'daemon'. >> > >> >> I gathered that. However in login.conf: >> >> daemon:\ >> :ignorenologin:\ >> :datasize=infinity:\ >> ^^^^^^^^^^^^^^^^^^^^ >> :maxproc=infinity:\ >> :openfiles-cur=128:\ >> :stacksize-cur=8M:\ >> :localcipher=blowfish,8:\ >> :tc=default: >> >> Also ps(1) output seems to confirm that named process limit is the >> entire memory of the machine. >> >> root@openbsd: /var/named/tmp # ps -ax -v | head >> PID STAT TIME SL RE PAGEIN VSZ RSS LIM TSIZ %CPU %MEM COMMAND >> 31077 S 277:43.57 0 127 15 608272 610340 8145988 1292 10.6 7.3 >> /usr/sbin/named > > lim is "memory" not "datasize". > > Considering the amount of memory this process is actually using, it > looks to me more like it's being run with a 512MB datasize limit, > so perhaps it's not running under the expected 'daemon' class. >
Thanks Stuart, this seems reasonable. How can I find under what class the named process is? Study the sources? > BTW, under OpenBSD/amd64 the most the datasize for a single process > can be without modifying the kernel is 8GB. > Interesting. Regards, Kostas -- Kostas Zorbadelos twitter:@kzorbadelos http://gr.linkedin.com/in/kzorba ---------------------------------------------------------------------------- () www.asciiribbon.org - against HTML e-mail & proprietary attachments /\
