Re: limits puzzle - different limits on similar machines
On Wed, Aug 24, 2005 at 09:46:44PM -0400, Chuck Swiger wrote: Danny Howard wrote: On Tue, Aug 23, 2005 at 06:52:28PM -0600, Chad Leigh -- Shire.Net LLC wrote: On Aug 23, 2005, at 5:56 PM, Danny Howard wrote: # bump max datasize options MAXDSIZ=(1024*1024*1024) options MAXSSIZ=(1024*1024*1024) options DFLDSIZ=(1024*1024*1024) Might this not be it? unlimited is really limited by the kernel sys params [ ... ] We can't tune the kernel limits through sysctl, eh? :) No, but see /boot/default/loader.conf, you can tune it there without having to rebuild the kernel... That much I know, but what variables? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: limits puzzle - different limits on similar machines
On Aug 25, 2005, at 3:13 PM, Danny Howard wrote: No, but see /boot/default/loader.conf, you can tune it there without having to rebuild the kernel... That much I know, but what variables? kern.dfldsiz is probably the most crucial one, but a more complete list would be: #kern.dfldsiz=# Set the initial data size limit #kern.dflssiz=# Set the initial stack size limit #kern.hz=100 # Set the kernel interval timer rate #kern.maxbcache= # Set the max buffer cache KVA storage #kern.maxdsiz=# Set the max data size #kern.maxfiles= # Set the sys. wide open files limit #kern.maxproc=# Set the maximum # of processes #kern.maxssiz=# Set the max stack size #kern.maxswzone= # Set the max swmeta KVA storage #kern.maxtsiz=# Set the max text size It's used like so: 9-pi% cat /boot/loader.conf kern.dfldsiz=1G kern.hz=1000 -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: limits puzzle - different limits on similar machines
On Tue, Aug 23, 2005 at 06:52:28PM -0600, Chad Leigh -- Shire.Net LLC wrote: On Aug 23, 2005, at 5:56 PM, Danny Howard wrote: # bump max datasize options MAXDSIZ=(1024*1024*1024) options MAXSSIZ=(1024*1024*1024) options DFLDSIZ=(1024*1024*1024) Might this not be it? unlimited is really limited by the kernel sys params Chad, Ayup, though I swear yesterday I was getting unlimited values for root across the board, and only seeing limits for users. But now I always see the same limits for root. So ... yeah, its the kernel. We can't tune the kernel limits through sysctl, eh? :) -danny -- http://dannyman.toldme.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: limits puzzle - different limits on similar machines
Danny Howard wrote: On Tue, Aug 23, 2005 at 06:52:28PM -0600, Chad Leigh -- Shire.Net LLC wrote: On Aug 23, 2005, at 5:56 PM, Danny Howard wrote: # bump max datasize options MAXDSIZ=(1024*1024*1024) options MAXSSIZ=(1024*1024*1024) options DFLDSIZ=(1024*1024*1024) Might this not be it? unlimited is really limited by the kernel sys params [ ... ] We can't tune the kernel limits through sysctl, eh? :) No, but see /boot/default/loader.conf, you can tune it there without having to rebuild the kernel... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
limits puzzle - different limits on similar machines
Hello, We have a process that runs fine on one machine but then dies on another, spitting an out-of-memory error. Interestingly, the limits for the user are higher on the working machine and lower on the other. So, I try to puzzle out why, reading all about login.conf, but login.conf is the same on every machine I visit, and it sets datasize=unlimited ... 1-16:35 [EMAIL PROTECTED] ~ uname -a grep datasize /etc/login.conf limits FreeBSD mito.sr._.com 5.4-STABLE FreeBSD 5.4-STABLE #3: Fri Jul 29 16:05:16 PDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MITO i386 :datasize=unlimited:\ # :datasize-cur=22M:\ # :datasize=8M:\ # :datasize=12M:\ # :datasize=infinity:\ # :datasize=infinity:\ # :datasize-cur@:\ # :datasize-cur=64M:\ # :datasize=2M:\ Resource limits (current): cputime infinity secs filesize infinity kb datasize 524288 kb stacksize 65536 kb coredumpsize infinity kb memoryuseinfinity kb memorylocked infinity kb maxprocesses 3632 openfiles7264 sbsize infinity bytes vmemoryuse infinity kb Okay, but on a different machine, the machine that runs the tricky process: 1-16:36 [EMAIL PROTECTED] ~ uname -a grep datasize /etc/login.conf limits FreeBSD bali.web.sr._.com 4.8-STABLE FreeBSD 4.8-STABLE #1: Mon Apr 21 1 3:36:32 PDT 2003 [EMAIL PROTECTED]:/local0/world/obj/local0/wor ld/src/sys/BALI i386 :datasize=unlimited:\ # :datasize-cur=22M:\ # :datasize=8M:\ # :datasize=12M:\ # :datasize=infinity:\ # :datasize=infinity:\ # :datasize-cur@:\ # :datasize-cur=64M:\ # :datasize=2M:\ Resource limits (current): cputime infinity secs filesize infinity kb datasize 1048576 kb stacksize 1048576 kb coredumpsize infinity kb memoryuseinfinity kb memorylocked infinity kb maxprocesses 5547 openfiles 11095 sbsize infinity bytes vmemoryuse infinity kb Others? 0-19:37 [EMAIL PROTECTED] ~ uname -a grep datasize /etc/login.conf limits FreeBSD web3.web._.com 4.10-RELEASE-p2 FreeBSD 4.10-RELEASE-p2 #1: Thu O ct 21 18:39:52 EDT 2004 [EMAIL PROTECTED]:/local0/world/obj/local0 /world/src/sys/WEB3 i386 :datasize=unlimited:\ # :datasize-cur=22M:\ # :datasize=8M:\ # :datasize=12M:\ # :datasize=infinity:\ # :datasize=infinity:\ # :datasize-cur@:\ # :datasize-cur=64M:\ # :datasize=2M:\ Resource limits (current): cputime infinity secs filesize infinity kb datasize 524288 kb stacksize 65536 kb coredumpsize infinity kb memoryuseinfinity kb memorylocked infinity kb maxprocesses 5547 openfiles 11095 sbsize infinity bytes vmemoryuse infinity kb 0-16:21 [EMAIL PROTECTED] ~ uname -a grep datasize /etc/login.conf limits FreeBSD rahu.web.sr._.com 4.9-STABLE FreeBSD 4.9-STABLE #1: Mon Mar 22 1 3:38:20 PST 2004 [EMAIL PROTECTED]:/local0/world/obj/local0/wor ld/src/sys/RAHU i386 :datasize=unlimited:\ # :datasize-cur=22M:\ # :datasize=8M:\ # :datasize=12M:\ # :datasize=infinity:\ # :datasize=infinity:\ # :datasize-cur@:\ # :datasize-cur=64M:\ # :datasize=2M:\ Resource limits (current): cputime infinity secs filesize infinity kb datasize 524288 kb stacksize 65536 kb coredumpsize infinity kb memoryuseinfinity kb memorylocked infinity kb maxprocesses 5547 openfiles 11095 sbsize infinity bytes vmemoryuse infinity kb I originally suspected that the login class was being set differently on different systems based on whether the system was a NIS client or if the user was in master.passwd ... in neither case have I bothered setting a login class ... but in the above output, rahu and bali are NIS clients, web3 and mito are not ...and mito has differing maxprocesses and openfiles from other 5.x hosts .. why? Could it be the kernel build? 0-16:46 [EMAIL PROTECTED] ~ diff /usr/src/sys/i386/conf/GENERIC /usr/src/sys/i386/conf/MITO 2c2 # GENERIC -- Generic kernel configuration file for FreeBSD/i386 --- # MITO -- Generic kernel configuration file for FreeBSD/i386 19c19 # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.413.2.13 2005/04/02 16:37:58 scottl Exp $ --- # $FreeBSD: src/sys/i386/conf/MITO,v 1.413.2.8 2004/10/24 17:42:08 scottl Exp $ 25c25 ident GENERIC --- ident MITO 28c28 #hintsGENERIC.hints # Default places to look for devices. --- #hintsMITO.hints# Default places to look for devices. 61c61 deviceapic# I/O APIC --- device
Re: limits puzzle - different limits on similar machines
On Aug 23, 2005, at 5:56 PM, Danny Howard wrote: # bump max datasize options MAXDSIZ=(1024*1024*1024) options MAXSSIZ=(1024*1024*1024) options DFLDSIZ=(1024*1024*1024) Might this not be it? unlimited is really limited by the kernel sys params Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
